Authentication

The MCP server supports two authentication methods: OAuth 2.0 for interactive use and API keys for programmatic access.

OAuth 2.0

MCP clients that support OAuth (such as Claude, ChatGPT, and Microsoft Copilot) handle the authentication flow automatically using Dynamic Client Registration. When connecting for the first time, you will be prompted to:

1. Sign in to your Entropy Data account
2. Consent to permissions — review and accept the data access permissions
3. Select organization — choose which organization to connect to

Claude

In Claude, go to Settings > Connectors and add a custom connector with your MCP Server URL. Claude uses Dynamic Client Registration — no client ID or secret is needed.

OAuth endpoints

For MCP clients that require manual OAuth configuration:

API Key

As an alternative to OAuth, you can authenticate using a user-bound API key. This is useful for programmatic access or when your MCP client does not support OAuth.

Requirements:

• The API key must be associated with a user (organization-level keys are not supported for MCP)
• The user must be a member of the organization

Include the x-api-key header in your MCP requests:

x-api-key: ed_your_api_key_here

API keys can be managed in the Entropy Data UI under Settings > API Keys.

Claude Code CLI

claude mcp add --transport http entropy-data https://app.entropy-data.com/mcp --header "x-api-key: ed_your_api_key_here"

MCP client configuration

Add the following to your claude_desktop_config.json or .mcp.json:

{
  "mcpServers": {
    "entropy-data": {
      "url": "https://app.entropy-data.com/mcp",
      "headers": {
        "x-api-key": "ed_your_api_key_here"
      }
    }
  }
}