Use DataQuoll from your AI tools

Where: .mcp.json (project) or ~/.claude.json

One command. Add --scope project to commit the server to a repo for a team, or --scope user to have it in every project.

claude mcp add --transport http dataquoll https://dataquoll.io/api/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Where: .cursor/mcp.json (project) or ~/.cursor/mcp.json

Cursor reads ${env:...} from your shell, so export DATAQUOLL_API_KEY before launching it and the key never sits in a file.

{
  "mcpServers": {
    "dataquoll": {
      "url": "https://dataquoll.io/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:DATAQUOLL_API_KEY}"
      }
    }
  }
}

Where: .vscode/mcp.json

The key is servers, not mcpServers. The inputs block prompts for the key once and keeps it in the secret store, which is what the VS Code docs recommend over a literal.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "dataquoll-key",
      "description": "DataQuoll API key",
      "password": true
    }
  ],
  "servers": {
    "dataquoll": {
      "type": "http",
      "url": "https://dataquoll.io/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:dataquoll-key}"
      }
    }
  }
}

Where: ~/.codex/config.toml

Codex takes the NAME of an environment variable, not the key. Export DATAQUOLL_API_KEY before starting Codex; it reads the variable at launch, not per call.

[mcp_servers.dataquoll]
url = "https://dataquoll.io/api/mcp"
bearer_token_env_var = "DATAQUOLL_API_KEY"

Where: ~/.codeium/windsurf/mcp_config.json

Windsurf names the URL key serverUrl. It interpolates ${env:...} the same way Cursor does.

{
  "mcpServers": {
    "dataquoll": {
      "serverUrl": "https://dataquoll.io/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:DATAQUOLL_API_KEY}"
      }
    }
  }
}

Where: settings.json

Zed calls them context_servers. With the header set it connects directly; without one it would try an OAuth flow this server does not have.

{
  "context_servers": {
    "dataquoll": {
      "url": "https://dataquoll.io/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Where: claude_desktop_config.json

Claude Desktop cannot attach a header to a remote server itself (its connector UI takes a URL and OAuth only), so it goes through the mcp-remote bridge. The header is written with NO space after the colon; that is how mcp-remote splits it.

{
  "mcpServers": {
    "dataquoll": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://dataquoll.io/api/mcp",
        "--header",
        "Authorization:Bearer YOUR_API_KEY"
      ]
    }
  }
}

Where: the client's MCP configuration

The shape every Streamable HTTP client understands. The endpoint goes in url and the key in an Authorization header; that is the whole configuration.

{
  "url": "https://dataquoll.io/api/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_API_KEY"
  }
}