Developer · Local MCP server
GraphPilot
Structural memory for coding agents: callers, callees, blast radius and symbols over MCP.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.graphpilot-oss/graphpilot- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-06-05
- Updated
- 2026-06-05
- Publisher
- graphpilot-oss (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/graphpilot-oss) · how
- Website
- github.com/graphpilot-oss/graphpilot#readme
- Repository
- github.com/graphpilot-oss/graphpilot
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @graphpilot-oss/graphpilot | 1.0.1 | stdio |
How to connect GraphPilot
GraphPilot runs locally from a Node.js package published to the npm registry: @graphpilot-oss/graphpilot version 1.0.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @graphpilot-oss/graphpilot@1.0.1. It reads the environment variable GRAPHPILOT_ROOT; set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"graphpilot": {
"command": "npx",
"args": [
"-y",
"@graphpilot-oss/graphpilot@1.0.1"
],
"env": {
"GRAPHPILOT_ROOT": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| GramClawManage Telegram outreach, campaigns, follow-ups, conversations, and pipelines from an MCP client. | Remote · HTTP |
| GranethPre-flight check for AI coding agents: hallucinated packages + secrets, 6 ecosystems, no account. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| GraphifySearch indexed code, trace dependencies, assess change impact, and recall repository memory. | Remote · HTTPLive check: sign-in required |
| GraphkeeperMines git history for file co-change patterns into a queryable knowledge graph via MCP. | Local · stdio |
| GraphqlTurn any GraphQL API into MCP tools. Zero config, zero code. | Local · stdio |
| graphyCompile any codebase into a walkable graph and serve it over MCP. No model decides an edge. | Local · stdio |
| GraqleGraph-powered codebase reasoning, impact analysis, and governance tools over MCP. | Local · stdio |
| Grasp - Code Architecture & Dependency AnalysisCodebase analysis: dependency graphs, security scanning, and refactor plans for GitHub and GitLab. | Local · stdio |