Data Explorer · MCP API

Connect to /mcp

Copy-paste setup for the MCP clients we test against.

Authentication

Every call to /mcp needs a bearer token in the Authorization header. Tokens are 51 characters in the format dz_pk_<lookup>_<secret> — the dz_pk_ prefix lets log scrubbers spot accidental leaks.

How to get a token

Tokens are admin-issued in v1. A self-service token UI is on the roadmap; until then, contact the team to request access.

Claude Code (CLI)

Run this once. Replace the placeholder with your real token.

shell
claude mcp add --transport http deving-zone https://deving.zone/mcp \
  --header "Authorization: Bearer dz_pk_xxxxxxxxxxxx_yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy"

Or, edit ~/.claude.json directly

Add an entry under the top-level "mcpServers" key:

~/.claude.json
{
  "mcpServers": {
    "deving-zone": {
      "type": "http",
      "url": "https://deving.zone/mcp",
      "headers": {
        "Authorization": "Bearer dz_pk_xxxxxxxxxxxx_yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy"
      }
    }
  }
}

n8n

In your n8n MCP node, configure the URL and a "Bearer" credential:

n8n MCP node config
{
  "serverUrl": "https://deving.zone/mcp",
  "authentication": "bearerToken",
  "bearerToken": "dz_pk_xxxxxxxxxxxx_yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy"
}

See n8n MCP node docs