Server URL
Discovery
We publish discovery metadata so MCP-compatible agents can detect the server, its tools, and its auth method automatically:- Server card: https://www.datalegion.ai/.well-known/mcp/server-card.json (per SEP-1649)
- Manifest pointer: https://www.datalegion.ai/.well-known/mcp.json
Authentication
You can connect in three ways:- Sign in with your Data Legion account. Claude, ChatGPT, Claude Code, Codex and Grok open a Data Legion sign-in page the first time you use the server. No key to copy or store. Signing in gives the assistant its own API key, scoped to enrich and search, on the team you choose. Manage these on the Connected Apps page.
- Send an API key. Every other MCP client passes a key in the
API-Keyheader, the same way the REST API works. Create keys on the API Keys page. - Let an agent get its own key. An AI agent can follow datalegion.ai/auth.md: you approve it by reading back a short code, and it gets its own API key on the team you choose, which it sends in the
API-Keyheader. Each agent you approve is listed on the Connected Apps page, where you can disconnect it.
Setup
Claude (web, desktop and mobile)
On a Free, Pro or Max plan:- Go to Customize → Connectors and click Add custom connector.
- Enter
https://api.datalegion.ai/mcp. If asked for an OAuth client, choose Use Claude’s published identity. - Click Add, then Connect. Claude opens a Data Legion sign-in page; sign in and approve access.
Claude Code
Add the server, then sign in from inside Claude Code:/mcp, select datalegion, and choose Authenticate. Claude Code opens the sign-in page in your browser.
To use an API key instead, add it as a header:
Add to your project’s .mcp.json:
Cursor
Open Cursor Settings → MCP, add a new server with namedatalegion, transport HTTP, URL https://api.datalegion.ai/mcp, and add an API-Key header with your key. Or paste this into your project’s .cursor/mcp.json:
ChatGPT
- In ChatGPT, open Settings → Security and login and turn on Developer mode. Your workspace admin may need to allow it.
- Go to chatgpt.com/plugins, select the plus button, and enter a name and description.
- Under Connection, enter
https://api.datalegion.ai/mcp, then create the connection. ChatGPT opens a Data Legion sign-in page; sign in and approve access.
Codex
Add the server:codex mcp login datalegion. In the Codex app or IDE extension, add the server under Settings → MCP servers (Add server, Streamable HTTP, then the URL) and choose Authenticate. Codex signs in as ChatGPT, so it shares ChatGPT’s entry on the Connected Apps page.
To use an API key instead, add this to ~/.codex/config.toml and set DATALEGION_API_KEY in your environment:
Grok
- Go to grok.com/connectors, choose New Connector, then Custom.
- Enter
https://api.datalegion.ai/mcpand save. Grok opens a Data Legion sign-in page; sign in and approve access.
Vercel
Add Data Legion from Connect → Browse Connectors in your Vercel team, then choose a connection method:- API Key. Paste a key from the API Keys page. Your deployed code gets the key at runtime from Vercel Connect and sends it in the
API-Keyheader tohttps://api.datalegion.aiorhttps://api.datalegion.ai/mcp. - Sign in. Sign in with your Data Legion account (admin or developer role) and request the
offline_accessscope so the connection stays signed in. Your code gets an access token from Vercel Connect and sends it as a Bearer token tohttps://api.datalegion.ai/mcp. This method works with the MCP server only. Choose the team whose credits Vercel uses on the Connected Apps page.
Gemini CLI
In your~/.gemini/settings.json (or workspace settings):
OpenClaw
OpenClaw discovers MCP servers via the standard MCP config block. Add this to your OpenClawmcp.json:
Other MCP-compatible clients
Cline, Continue, Windsurf, Goose, and any other client that speaks Model Context Protocol over Streamable HTTP work the same way: point them athttps://api.datalegion.ai/mcp and pass your key in the API-Key header. The server-card at /.well-known/mcp/server-card.json advertises capabilities and tools so compatible clients can connect with no further configuration.
Available Tools
The MCP server exposes 9 tools that map directly to the Data Legion REST API endpoints. Credits are consumed the same way as direct API calls. The natural-language/person/discover and /company/discover REST endpoints are not exposed via MCP today; call them from the REST API or SDKs.
Person
Company
Utilities
Reporting
Reporting has no credit cost and works whether you signed in or sent an API key.
Example Conversations
Once connected, you can ask your AI assistant things like:- “Look up the person with email jane.doe@acme.com”
- “Find software engineers in San Francisco who worked at Google”
- “Enrich the company google.com”
- “Search for AI startups with more than 50 employees”
- “Clean and validate this contact: email john.doe+work@gmail.com, phone (555) 123-4567”
- “Hash the email john@example.com for a privacy-safe lookup”
Credits
MCP tool calls consume credits at the same rate as the corresponding REST API endpoints.Managing Connected Apps
The Connected Apps page lists each assistant you signed in from, the team whose credits it uses, and when it connected. From there you can:- Switch an assistant to another team.
- Disconnect an assistant. Its key stops working right away, and it stays disconnected until you connect it again from this page.