READ
get_project_context
Returns the approved Problem Case, current MVP Design, architecture, features, tasks, tests, and delivery checklist.
Project-scoped MCP
Your coding agent is only as good as the context you give it.
Connect a completed Immensity Design to an MCP-compatible IDE and give the agent the approved problem, solution architecture, task graph, acceptance checks, and release context.
{
"mcpServers": {
"immensity": {
"command": "npx",
"args": ["-y", "immensity-mcp-server"],
"env": {
"IMMENSITY_PROJECT_TOKEN": "••••••••"
}
}
}
}3 tools available
The MCP surface
Three tools. One approved project.
READ
get_next_task
Returns the next incomplete task whose dependencies are finished.
WRITE
update_task_progress
Saves todo, in-progress, blocked, or done status with an optional implementation note.
Security by boundary
One connection. One project. Easy to revoke.
Project scoped
The connection cannot access another Project.
Shown once
Tokens are displayed once and stored only as SHA-256 hashes.
Time limited
Every connection expires automatically after 30 days.
Revocable
Disconnect the coding agent from Design whenever you need to.
Setup
From Design to your IDE in four moves.
- 01
Complete Analysis
Approve the cited Problem Case.
- 02
Complete Design
Approve the MVP, architecture, and task graph.
- 03
Create a connection
Generate the project-scoped token in Design.
- 04
Paste the configuration
Add Immensity to your MCP-compatible development environment.
Current boundary
Explore, Analysis, and Design happen in Immensity. MCP begins when the approved project is ready to build.
Ready for the handoff?
Give the agent the project—not another vague prompt.
Start with evidence and connect when the Design is approved.
Create a project