Model Context Protocol

Model Context Protocol (MCP) Integration

Orcha Agent OS is natively equipped with an MCP server interface (/api/mcp). Connect Claude Desktop, Cursor, Windsurf, or any MCP-compatible client directly to your database semantic layer.

MCP Native Architecture

Rather than maintaining custom agent connectors, Orcha implements the open Model Context Protocol specification. External AI tools can list available database query tools, inspect dynamic input schemas, and execute pre-validated SQL queries with just-in-time credential resolution.

Connecting Claude Desktop

Add Orcha to your claude_desktop_config.json file:

json
{
  "mcpServers": {
    "orcha-agent-os": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "http://localhost:3000/api/mcp",
        "--header",
        "Authorization: Bearer YOUR_ORCHA_API_KEY"
      ]
    }
  }
}

Connecting Cursor & Windsurf

Configure your workspace .cursor/mcp.json or Windsurf configuration settings:

json
{
  "mcpServers": {
    "orcha-database": {
      "url": "http://localhost:3000/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ORCHA_API_KEY"
      }
    }
  }
}

Dynamic Tool Schemas

When an MCP client issues listTools, Orcha inspects the organization's active database configurations and generates tailored JSON Schema tools for:

  • query_database - Executes governed SQL across mapped databases.
  • get_table_schema - Returns curated column definitions and business descriptions.
  • list_databook_queries - Retrieves verified golden queries from the organization catalog.

Security & Permission Scoping

Every MCP request is authenticated against an organization API key. Keys can be scoped to specific databases, rate-limited, and restricted to read-only queries with dry-plan validation.