initrepo-mcp
v2.0.0
Published
MCP stdio bridge for InitRepo — exposes your generated project documents to AI agents (Claude Code, Cursor, …) over the Model Context Protocol.
Maintainers
Readme
initrepo-mcp
An MCP server that exposes your InitRepo project documents to AI coding agents — Claude Code, Cursor, Cline, and anything else that speaks the Model Context Protocol.
Instead of pasting your planning documents into the agent at the start of every session, the agent reads them on demand: business analysis, PRD, UX/UI spec, technical architecture, user stories, roadmap, and the coordinate-addressed context index.
Prerequisites
- An InitRepo API key — create one on your account page (any paid plan; keys keep working with documents you generated even after a subscription ends).
- A project id — shown on your project's page in the InitRepo dashboard.
- Node.js 18 or newer.
Configure your agent
Claude Code
In your project's .claude/settings.json:
{
"mcpServers": {
"initrepo": {
"command": "npx",
"args": ["initrepo-mcp"],
"env": {
"INITREPO_API_KEY": "irk_live_your_key_here",
"INITREPO_PROJECT_ID": "your_project_id"
}
}
}
}Cursor and other clients
Add an MCP server with command npx initrepo-mcp and the same two environment
variables. Keep the API key out of version control — reference it from your
environment rather than committing it.
Environment variables
| Variable | Required | Description |
| --- | --- | --- |
| INITREPO_API_KEY | yes | A key from your InitRepo account page. |
| INITREPO_PROJECT_ID | yes | The project to expose to the agent. |
| INITREPO_ENDPOINT | no | Override the MCP endpoint URL (advanced). |
What the agent can do
- Resources — list and read each generated document plus
context_index.json. - Tool
get_step_context— given aP#S#coordinate (e.g.P1S3), return every document span tagged to that build step in a single call.
Access is read-only.
How it works
The bridge is a transparent stdio↔HTTP proxy: it reads newline-delimited JSON-RPC from the agent on stdin, forwards each message to the InitRepo MCP HTTP endpoint with your API key and project id attached, and relays the response on stdout. All protocol behavior lives server-side.
License
MIT
