🚧 Prototype
The Dataddo MCP server is an early prototype. See the Dataddo MCP Server overview for its current capabilities and roadmap.
Connect the Dataddo MCP server to Claude as a custom connector. Custom connectors added to your Claude account work in the claude.ai web app, Claude Desktop, and Claude mobile, and are available on all plans (Free users are limited to one custom connector).
⚠️ Authentication limitation
Claude custom connectors authenticate via OAuth or connect without authentication. Sending a static API token header ("Request headers") is currently an Anthropic beta with gradual rollout, so the option may not appear in your account yet. Without it, you are limited to tools that do not access account data (such as
current-time). If you use Claude Code, static tokens are fully supported - see Dataddo MCP in Claude Code.
Setup
On Free, Pro, and Max plans:
- In Claude, go to Settings → Connectors.
- Click Add custom connector.
- Enter:
- Name:
Dataddo - URL:
https://headless.dataddo.com/mcp
- Name:
- If your account shows a Request headers section (beta), add a required header
Authorizationwith the valueBearer <YOUR_ACCESS_TOKEN>- include theBearerprefix. To obtain a token, see Headless API Authorization. - Click Add.
On Team and Enterprise plans, an admin adds the connector first under Admin settings → Connectors; members then enable it under Settings → Connectors → Connect.
To use the connector in a chat, click the + button in the chat input, open Connectors, and enable Dataddo for the conversation.
Try It Out
Ask Claude:
Using the Dataddo tools, what is the current time in UTC?
Notes
- Claude Desktop uses the same account-level connector configuration as claude.ai - you do not edit
claude_desktop_config.jsonfor remote servers. - Claude connects to the Dataddo MCP server from Anthropic's cloud infrastructure, not from your device, so no local network configuration is needed.
Troubleshooting
- The connector fails to connect. Verify the URL is exactly
https://headless.dataddo.com/mcp. - Tools return authentication errors. Your access token may have expired; update the header value with a fresh token. See Authorization.