MCP Server
Mapnostics ships a native Model Context Protocol (MCP) server, hosted at mapnostics.com/api/mcp. Connect any MCP-compatible AI agent β Claude, Cursor, Zed β and it gets direct access to your codebase intelligence.
Connecting
First create a personal API key under Settings β API keys (keys look like mns_β¦ and are shown once at creation). Clients with native streamable-HTTP support connect directly:
For clients that only speak stdio, use the bridge β it forwards stdio messages to the hosted endpoint using the API key in your environment:
Live demo
Watch the MCP server connect, expose its tools, then answer a natural language query about your codebase β all in real time.
Available MCP tools
- get_repo_health β health score, dead code count, and tech debt hours for a repository.
- get_dead_code β dead code entities with evidence, confidence, and uncertainty reasons.
- get_zombie_code β zombie code entities with call-chain reachability paths.
- get_impact β given a file, returns the full blast radius: affected files with evidence.
- get_dependencies β the file import graph, for the whole repo or a single file.
- resolve_operational_truth β full reasoning trace for a single entity: rules evaluated, conclusion, why.
- get_intent β the AI-recovered intent summary for the repo or any file.
- get_health_score β composite health score with the per-dimension breakdown (same formula as the dashboard).
- detect_secrets β hardcoded secret findings from the latest scan, filterable by severity.
- get_onboarding β the graph-grounded onboarding guide: entry points, learning path, gotchas.
Compatible clients
Claude Code & Claude Desktop
Claude Code connects natively: claude mcp add --transport http mapnostics https://mapnostics.com/api/mcp --header "Authorization: Bearer mns_...". Claude Desktop uses the stdio bridge β add npx mapnostics-mcp to your claude_desktop_config.json with MAPNOSTICS_API_KEY in its env.
Cursor
Configure the server in .cursor/mcp.json β either the URL with an Authorization header, or the npx mapnostics-mcp bridge. Cursor will call Mapnostics tools automatically when answering questions about your codebase.
Any MCP-compatible agent
The server implements MCP over streamable HTTP; the bridge covers stdio-only clients. Any client that follows the protocol can connect β including custom agents built with the Anthropic Claude SDK or open-source MCP libraries.
Authorization: Bearer mns_β¦). Create and revoke keys under Settings β API keys; revocation takes effect immediately.