stellarion_find_entry_points

Identifies the top-level entry points of your application — the functions where execution begins. Finds main functions, HTTP route handlers, CLI command handlers, event listeners, and similar constructs across languages.

When to Use

• You are new to a codebase and want to understand its structure from the top down
• You need to find all HTTP endpoints in a web application
• You want to map out CLI commands and subcommands
• You are looking for event handlers or lifecycle hooks
• You want to trace execution from the entry point down using stellarion_get_callees

Parameters

Examples

Find all entry points in the project

Natural language:

What are the entry points of this application?

MCP call:

{
  "tool": "stellarion_find_entry_points",
  "arguments": {}
}

Find HTTP handlers in the API directory

Natural language:

Find all HTTP route handlers in the api directory

MCP call:

{
  "tool": "stellarion_find_entry_points",
  "arguments": {
    "scope": "src/api"
  }
}

Find CLI commands

Natural language:

What CLI commands does this application expose?

MCP call:

{
  "tool": "stellarion_find_entry_points",
  "arguments": {
    "scope": "cmd"
  }
}

Output Format

Returns a list of entry points:

• name — Function or handler name
• kind — Entry point type (main, http_handler, cli_command, event_handler, etc.)
• uri — File path
• line — Line number
• metadata — Additional context such as HTTP method and route path, CLI command name, or event type

Tips

• This is a great first call when exploring an unfamiliar project — it gives you the top-level structure immediately.
• Follow up with stellarion_get_callees on individual entry points to trace the full execution flow.
• Use scope to focus on specific parts of a monorepo or multi-module project.
• Entry point detection is language-aware: it recognizes fn main() in Rust, if __name__ == "__main__" in Python, Express/Fastify route registrations in JavaScript, and similar patterns across supported languages.