FastAPI Architect MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_referencesB | Find all references to the symbol at the given position across the project. |
| rename_symbolC | Rename the symbol at the given position across all files in the project. |
| go_to_definitionA | Return the file and line where the symbol at the given position is defined. |
| get_completionsC | Return completion suggestions at the given cursor position. |
| list_routesC | List all FastAPI routes across the entire project, with full paths (router prefixes applied). |
| get_dependenciesA | Get the full Depends() injection tree for a FastAPI handler across the entire project. Includes router-level, include_router, decorator-level and signature dependencies.
|
| list_modelsC | List all Pydantic BaseModel classes defined in a file. |
| inspect_modelB | Inspect a Pydantic model: fields with types/defaults, and validators. |
| find_model_usagesC | Find all places a Pydantic model is used as a type annotation across the project. |
| validate_response_modelsC | Detect FastAPI routes missing a response_model declaration. |
| build_dependency_graphB | Build a full dependency graph for the routes of a file: route → handler → dependencies → models. |
| detect_schema_orm_mismatchesC | Detect field mismatches between a SQLAlchemy ORM model and a Pydantic schema. |
| build_knowledge_graphA | Build or refresh the project's FastAPI knowledge graph and return its statistics. The graph links routes, handlers, dependencies, schemas, ORM models, SQL tables, templates and function calls. It is cached in /.fastapi-architect/ and only changed files are re-parsed, so other graph tools are fast. Use force=True to rebuild from scratch. |
| graph_neighborsA | Explore the knowledge graph around a node.
|
| impact_analysisB | What is affected if Follows reverse edges (callers, users, dependents, subclasses, mirroring schemas, tables → models).
Each impacted route includes a |
| find_pathC | Shortest paths between two nodes, e.g. from a route to a table ("POST /chat" → "chat_logs"). Directed paths are tried first; if none exists, direction is ignored and |
| audit_graphA | Project-wide checks: write routes without auth, duplicate routes, routers never mounted, unused schemas, unreferenced ORM models, dependency cycles and parse errors. Auth is inferred from dependency names, auth Header params and calls to auth-like functions.
Pass |
| graph_reportA | A concise Markdown overview of the project: stats, routes with their auth, hubs and audit findings. Good first call to understand an unfamiliar FastAPI codebase. With save=True the report is also written to /.fastapi-architect/GRAPH_REPORT.md. |
| export_graph_htmlA | Export the knowledge graph as a standalone interactive HTML page (open it in a browser). Nodes are colored by type (Route, Handler, Dependency, Schema, ORMModel, Table...), with search, type filters and a details panel listing each node's connections. Defaults to /.fastapi-architect/graph.html. Rendering loads vis-network from a CDN. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Each tool has a clearly distinct purpose: model inspection vs. listing, route enumeration vs. dependency trees, graph building vs. exploration, and audit vs. reporting. Even overlapping tools like impact_analysis and graph_neighbors differ in focus (impact vs. generic navigation). No ambiguity for agent selection.
The vast majority follow a consistent verb_noun snake_case pattern (inspect_model, list_routes, build_dependency_graph). A few like impact_analysis and graph_neighbors deviate slightly from the verb-first convention but remain predictable and readable, so only minor inconsistency.
19 tools is on the heavier side (borderline per rubric), but the FastAPI architecture domain is complex and the tool set covers analysis, refactoring, audit, graph exploration, and IDE-like features. Each tool earns its place; the count feels slightly large but not excessive.
The surface is highly complete for its purpose: covers model inspection/listing/usages, route enumeration/dependencies/validation, graph construction/exploration/impact/pathfinding, audit checks, reporting, and common IDE operations (references, completions, go-to-definition). No obvious dead ends or missing core capabilities.