Codapult MCP

Give your AI agent the map before it touches the code.

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.

Install MCP Read the documentation

Works with the agents you already use

Claude Code

Cursor

Codex

Windsurf

Gemini

VS Code

agent-sessionMCP · stdio

$ codapult mcp

> Inspect the billing architecture

● MCP · stdio · reading project context...

codapult_project_context

architecture · adapters · features

codapult://schema

codapult_doctor

Plan ready

✓ Working...

Context that compounds

Stop making your AI agent reverse-engineer your SaaS.

Generic repository tools see files. Codapult MCP exposes the system behind them: boundaries, state, conventions and safe operations.

Architecture

Understand modules, boundaries, adapters and conventions.

Database

Inspect schema, migrations, drift and relationships.

Project state

Read configuration, environment contracts and installed plugins.

Generation

Create pages, APIs, actions and plugins using Codapult patterns.

Discover

The agent sees project status, enabled features and installed modules.

Inspect

Resources expose schema, configuration, environment contract and conventions.

Change

Typed tools make generation, plugin and database work explicit and reviewable.

Verify

Doctor and check tools close the loop before code reaches production.

One command

Install MCP into your Codapult project.

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

Build SaaS faster with an agent that understands the system.

Get Codapult See all MCP tools

Built for Codapult projects from day one.