Claude · MCP
Connect Claude to your codebase.
Lander runs a Natural Graph extractor over your codebase on every push, mapping routes ↔ components ↔ APIs ↔ data. Your Claude connects to our MCP server and queries that graph before editing.
Claude Desktop
Add Lander to your Claude Desktop config. On macOS, that's ~/Library/Application Support/Claude/claude_desktop_config.json.
{
"mcpServers": {
"lander": {
"command": "npx",
"args": ["-y", "@lander/mcp-client"],
"env": {
"LANDER_API_KEY": "lndr_your_key_here"
}
}
}
}Restart Claude. You'll see Lander's tools (list_routes, get_route, etc.) in the tools panel.
Cursor
In Cursor settings, under MCP Servers:
{
"mcp": {
"lander": {
"url": "https://mcp.lander.host/<your-key>"
}
}
}What Claude can ask
list_routesEvery route in the codebase with its file path.
get_route(route)Components rendered + imports for a given route.
get_component(name)Where a component lives + which routes render it.
graph_neighbors(nodeId, depth)Adjacency lookup — useful for refactors.
find_data_source(field)Routes/components that read or write a given field.
Your API key lives in Settings. Rotate any time.