MCP Server

DataBlue MCP Server

Add the DataBlue connector to ChatGPT, Claude, or Codex and sign in with OAuth. No API key is copied into a hosted client.

Browser sign-in accepts a DataBlue company email and password, Google, or GitHub; a Google account is optional.

Your ChatGPT, Claude, or Codex email can be different from your DataBlue email. The consent screen shows which DataBlue account will own usage, plan limits, and history.

https://mcp.datablue.dev/mcp

ChatGPT

In ChatGPT web, open Settings -> Apps -> Create. If Create is unavailable, your workspace administrator must enable Developer mode; availability depends on your ChatGPT plan and workspace permissions.

Enter the hosted endpoint, choose OAuth, select Scan Tools, complete DataBlue browser sign-in, then create the app.

Claude

On an individual Free, Pro, or Max plan, open Customize -> Connectors -> + -> Add custom connector, then paste the hosted endpoint. Free plans support one custom connector.

On Team or Enterprise, an Owner or Primary Owner first adds the connector from Organization settings -> Connectors -> Add -> Custom -> Web. After that, members open Customize -> Connectors, find DataBlue, and select Connect to authenticate.

For Claude Code:

claude mcp add --transport http datablue https://mcp.datablue.dev/mcp
claude mcp login datablue

Codex

The ChatGPT desktop app and Codex IDE extension can add DataBlue from Settings -> MCP servers -> Add server. Choose Streamable HTTP, enter the endpoint, save, restart, and authenticate.

For Codex CLI:

codex mcp add datablue --url https://mcp.datablue.dev/mcp
codex mcp login datablue

The delegated grant requests mcp:tools for tools and usage:read for usage resources. Revoke it from Dashboard -> Settings -> Connected apps.

API key setup (advanced)

For non-interactive automation, a client may send an existing DataBlue API key as Authorization: Bearer YOUR_API_KEY to the hosted endpoint. Keep DATABLUE_API_KEY in the client's environment or secret store, never in source control or a tool argument.

Local setup (advanced)

Local mode requires Node.js 18.18 or newer and reads the API key from the MCP process environment.

DATABLUE_API_KEY="YOUR_API_KEY" npx --yes --prefer-online @datablue/mcp@latest

Standard MCP JSON configuration

{
  "mcpServers": {
    "datablue": {
      "command": "npx",
      "args": ["--yes", "--prefer-online", "@datablue/mcp@latest"],
      "env": { "DATABLUE_API_KEY": "YOUR_API_KEY" }
    }
  }
}

Codex local stdio

codex mcp add datablue --env DATABLUE_API_KEY=YOUR_API_KEY -- npx --yes --prefer-online @datablue/mcp@latest

Claude Code local stdio

claude mcp add --transport stdio datablue --env DATABLUE_API_KEY=YOUR_API_KEY -- npx --yes --prefer-online @datablue/mcp@latest

Choose a primitive