MCP Setup

The Conduit MCP server exposes Admin API operations as tools so AI agents can provision schemas, users, and config during development. Never call MCP from application runtime code.

Prerequisites

1. Running Conduit instance with Admin API reachable (default port 3030)
2. MCP transport enabled: transports.mcp: true in admin config
3. Admin JWT or cdt_ API token

Cursor configuration

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "conduit": {
      "url": "http://localhost:3030/mcp?modules=authentication,database,storage,authorization",
      "headers": {
        "Authorization": "Bearer YOUR_ADMIN_JWT_OR_cdt_TOKEN"
      }
    }
  }
}

Protocol: Streamable HTTP (2025-06-18). Path is fixed at /mcp.

Module loading

On connect, only core and __meta__ load by default. Enable modules via the URL query:

After changing the URL, reconnect MCP and call list_modules to verify loaded: true.

Authentication

• Admin JWT — from admin login flow
• API token — create via Admin API (cdt_ prefix, shown once)

Every request: Authorization: Bearer <token>.

Tool naming

Admin routes map to tools: GET /database/schemas → get_database_schemas.