Cross-project knowledge graph for MCP — map features across mobile, backend, and admin codebases.
Connect Project to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Cross-project knowledge graph for MCP — map features across mobile, backend, and admin codebases. The project mcp server is what makes that connection.
When working on a project with multiple codebases — for example, a React Native mobile app, a NestJS backend, and a Next.js admin panel — the AI agent has no awareness of how a single feature flows across all three. This leads to incomplete context, missed dependencies, and breaking changes that could have been caught earlier.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Validation — The Validation tool exposed by this serverPersistence — The Persistence tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at project-knowledge-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Project's toolset — Validation, Persistence — is a fair guide to whether it matches your workflow. It is maintained by batook22; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Project's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Validation | The Validation tool exposed by this server. |
| Persistence | The Persistence tool exposed by this server. |
Then add to your MCP settings:
```json
{
"mcpServers": {
"project-knowledge": {
"command": "npx",
"args": [
"-y",
"project-knowledge-mcp",
"--knowledge-file", "C:\\projects\\project-knowledge.json"
],
"autoApprove": []
}
}
}Configuration as documented by the project. Restart the client after saving.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.