Shelbymcp
Persist structured knowledge-graph memory so your agent recalls entities and relationships across long build sessions.
Overview
Shelby MCP is an MCP server for the Build phase that provides a knowledge-graph memory layer so AI agents store and query entities and relationships over stdio.
What is this MCP server?
- Knowledge-graph memory server designed for AI tools
- Stdio MCP via npx shelbymcp npm package
- Stores entities and relationships for later agent retrieval
- Version 0.2.4 on npm registry type
- Open-source Studio-Moser implementation on GitHub
- Published npm package version 0.2.4
- Stdio transport with npx runtimeHint and positional shelbymcp
- Described as knowledge-graph memory server for AI tools via MCP
What problem does it solve?
Long agent sessions drop prior decisions and architecture links, forcing expensive re-discovery from scratch each chat.
Who is it for?
Solo builders running multi-day agent workflows who want explicit structured memory beyond flat chat history.
Skip if: One-off scripts with no recurring context needs, or teams that require a hosted enterprise memory SaaS with compliance guarantees out of the box.
What do I get? / Deliverables
Your agent reads and writes a persistent knowledge graph so project facts and relationships survive across sessions.
- Queryable knowledge graph accessible from the agent
- Stored entities and relationships across sessions
- MCP tools for memory read/write in the build loop
Recommended MCP Servers
Journey fit
Durable agent memory is most often adopted while building products and automations where context spans many files and sessions, which is core Build-phase agent tooling. Shelby exposes memory primitives over MCP rather than business analytics; Agent-tooling is the shelf for augmenting recall and continuity in coding agents.
How it compares
Local knowledge-graph memory MCP, not a deploy control plane or LSP diagnostics bridge.
Common Questions / FAQ
Who is Shelby MCP for?
It is for developers using MCP agents who need durable, queryable memory of project entities and how they connect.
When should I use Shelby MCP?
Use it when starting a complex build or returning after a break and you want the agent to recall architecture, names, and relationships you stored earlier.
How do I add Shelby MCP to my agent?
Add a stdio MCP server entry that runs npx with positional argument shelbymcp (npm package shelbymcp), then use your client’s memory or graph tools as exposed by the server.