Skip to content

MCP server

Dezycro exposes a Model Context Protocol (MCP) server at https://mcp.dezycro.ai/mcp. The MCP server is what the Claude Code plugin talks to — but you can also use it directly from any MCP-compatible client (Cursor, Continue, custom IDE plugins, etc.).

Authentication

Use a Personal Access Token:

Authorization: Bearer dzy_<your-token>

Pass the header on every request. The MCP server resolves the PAT to your user + tenant + per-workspace permissions on each call — there's no separate workspace selection step.

Wiring up a client

Claude Code

claude mcp add dezycro \
  --transport http \
  --url https://mcp.dezycro.ai/mcp \
  --header "Authorization: Bearer dzy_..."

Or place this in ~/.claude/settings.json:

{
  "mcpServers": {
    "dezycro": {
      "type": "http",
      "url": "https://mcp.dezycro.ai/mcp",
      "headers": {
        "Authorization": "Bearer dzy_..."
      }
    }
  }
}

Other clients

Most MCP-compatible clients accept the same shape — point at https://mcp.dezycro.ai/mcp and pass the bearer header. The transport is Streamable HTTP (the modern MCP transport — initialize handshake, session ID, JSON-RPC over POST).

Available tools

The MCP server exposes the same tools the Claude Code plugin uses, covering discovery and search, feature and document management, the workbook, verification and coverage, test generation, notebooks, AI council reviews, and workspace metrics.

We deliberately don't enumerate them here: MCP tools are self-describing. Every tool ships its name, description, and full parameter schema over the protocol, and every MCP client fetches that list on connect (a standard tools/list call — Claude Code, Cursor, and friends do it automatically and show it in their tool browser). Since the consumers are agents, the in-protocol descriptions are the canonical, always-current reference — a hand-maintained copy here would only drift.

To eyeball the current set yourself, connect any MCP client, or:

npx @modelcontextprotocol/inspector \
  --transport http \
  --url https://mcp.dezycro.ai/mcp \
  --header "Authorization: Bearer dzy_..."

Quirks

  • Streamable HTTP transport — the first POST must be an initialize JSON-RPC call; the server returns a Mcp-Session-Id header. Subsequent calls must echo that header back. Standard MCP clients handle this automatically.
  • Per-workspace permission inheritance — your PAT inherits your workspace role on every call. A Viewer PAT can call get_* / list_* tools but not create_* / update_* ones.
  • Idempotency — update_document overwrites; add_* always creates a new entity. There's no append semantics on documents.
  • Long-running operations — generate_tests and publish_feature_spec return immediately; generation and verifier-binary compilation continue in the background. Poll list_test_cases / pull_verifier, or use the plugin's dezycro await-event CLI to block until the build event lands.