Skip to main content
New in version 2.9.0 fastmcp inspect loads a server and reports what it contains — its tools, resources, prompts, version, and metadata. The default output is a human-readable summary:

JSON Output

For programmatic use, two JSON formats are available: FastMCP format (--format fastmcp) includes everything FastMCP knows about the server — tool tags, enabled status, output schemas, annotations, and custom metadata. Field names use snake_case. This is the format for debugging and introspecting FastMCP servers. MCP protocol format (--format mcp) shows exactly what MCP clients see through the protocol — only standard MCP fields, camelCase names, no FastMCP-specific extensions. This is the format for verifying client compatibility and debugging what clients actually receive.

Options

Entrypoints

The inspect command supports the same local entrypoints as fastmcp run: inferred instances, explicit entrypoints, factory functions, and fastmcp.json configs.
inspect only works with local files and fastmcp.json — it doesn’t connect to remote URLs or standard MCP config files.