Codapult MCP
Codapult MCP is not a generic repository wrapper. It exposes the architecture, database, environment, plugins and deployment state of a Codapult project — so Cursor, Claude Code, Codex, Gemini and Windsurf can make changes that fit.
Works with the agents you already use
> Inspect the billing architecture
● MCP · stdio · reading project context...
codapult_project_context
architecture · adapters · features
codapult://schema
codapult_doctor
Plan ready
✓ Working...
MCP · stdio
Context that compounds
Generic repository tools see files. Codapult MCP exposes the system behind them: boundaries, state, conventions and safe operations.
Understand modules, boundaries, adapters and conventions.
Inspect schema, migrations, drift and relationships.
Read configuration, environment contracts and installed plugins.
Create pages, APIs, actions and plugins using Codapult patterns.
The agent sees project status, enabled features and installed modules.
Resources expose schema, configuration, environment contract and conventions.
Typed tools make generation, plugin and database work explicit and reviewable.
Doctor and check tools close the loop before code reaches production.
One command
MCP is specialized for Codapult projects. It is not a universal server that pretends every repository has the same architecture.
.cursor/mcp.json
{
"mcpServers": {
"codapult": {
"command": "npx",
"args": ["-y", "@codapult/cli@latest", "mcp-server"]
}
}
}$ codapult mcp doctor
Built for Codapult projects from day one.