Project Knowledge Mcp
Give your coding agent a shared map of features and dependencies across mobile, backend, and admin repos so changes stay aligned.
Overview
io.github.batook22/project-knowledge-mcp is a MCP server for the Build phase that maps features and relationships across mobile, backend, and admin codebases for agent queries.
What is this MCP server?
- stdio MCP server (npm package project-knowledge-mcp v1.0.6)
- Knowledge graph spanning mobile, backend, and admin codebases
- Feature-level mapping for agents working across repositories
- Designed for MCP clients that need project-wide context, not single-repo grep
- Server version 1.0.6
- Transport stdio via npm identifier project-knowledge-mcp
- Publisher registry schema 2025-12-11
Community signal: 1 GitHub stars.
What problem does it solve?
Agents and humans lose track of which repos implement the same feature when a product spans mobile, API, and admin apps.
Who is it for?
Solo builders maintaining a multi-repo stack who want MCP-backed feature maps during integration work.
Skip if: Single-repo prototypes or teams that already maintain a formal architecture wiki with no agent access needs.
What do I get? / Deliverables
Your agent can query a single cross-project knowledge graph instead of guessing from isolated repo searches.
- Queryable cross-project feature map inside the agent
- Aligned answers when changes touch mobile, backend, or admin
- Reduced repeated manual repo exploration per task
Recommended MCP Servers
Journey fit
Cross-repo feature mapping is introduced when you are wiring multiple codebases together during product build. Integrations subphase is where multi-project graphs and shared feature knowledge matter most for solo builders shipping full stacks.
How it compares
Cross-repo knowledge graph MCP server, not a generic code search or single-repository indexer.
Common Questions / FAQ
Who is project-knowledge-mcp for?
Indie and solo developers who run separate mobile, backend, and admin codebases and want their AI agent to understand how features line up across those projects.
When should I use project-knowledge-mcp?
Use it during build and integration work when you change features that span multiple repositories or when onboarding an agent to a full-stack product layout.
How do I add project-knowledge-mcp to my agent?
Add the npm stdio package project-knowledge-mcp to your MCP client configuration per the publisher repo punic-pillars/project-knowledge-mcp, then connect your project roots the server expects.