Skip to main content
The Data Legion MCP server lets AI assistants access your person and company data through tool calls. It works with any MCP-compatible client including Claude Code, Claude Desktop, ChatGPT, Codex, Grok, Gemini, Cursor, OpenClaw, Cline, Continue, Windsurf, and Goose.

Server URL

Discovery

We publish discovery metadata so MCP-compatible agents can detect the server, its tools, and its auth method automatically:

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-Key header, 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-Key header. Each agent you approve is listed on the Connected Apps page, where you can disconnect it.
Either way, credits and rate limits apply exactly as they do for direct API calls. Signing in needs the admin or developer role on your Data Legion account. If your account has more than one team, the assistant asks you to choose a team on the Connected Apps page the first time it connects.

Setup

Claude (web, desktop and mobile)

On a Free, Pro or Max plan:
  1. Go to Customize → Connectors and click Add custom connector.
  2. Enter https://api.datalegion.ai/mcp. If asked for an OAuth client, choose Use Claude’s published identity.
  3. Click Add, then Connect. Claude opens a Data Legion sign-in page; sign in and approve access.
On a Team or Enterprise plan, an Owner first adds the connector under Organization settings → Connectors (Add, then Custom). Each member then finds it under Customize → Connectors with the Custom label and clicks Connect to sign in. The tools are then available in conversations on the web, desktop and mobile apps, and in Cowork.

Claude Code

Add the server, then sign in from inside Claude Code:
Run /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:
Or via CLI:

Cursor

Open Cursor Settings → MCP, add a new server with name datalegion, 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

  1. In ChatGPT, open Settings → Security and login and turn on Developer mode. Your workspace admin may need to allow it.
  2. Go to chatgpt.com/plugins, select the plus button, and enter a name and description.
  3. 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.
ChatGPT then discovers the nine Data Legion tools and calls them automatically.

Codex

Add the server:
Codex opens a Data Legion sign-in page in your browser; to sign in again later, run 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

  1. Go to grok.com/connectors, choose New Connector, then Custom.
  2. Enter https://api.datalegion.ai/mcp and save. Grok opens a Data Legion sign-in page; sign in and approve access.
Grok then calls the Data Legion tools when a chat needs them. It has its own entry on the Connected Apps page.

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-Key header to https://api.datalegion.ai or https://api.datalegion.ai/mcp.
  • Sign in. Sign in with your Data Legion account (admin or developer role) and request the offline_access scope so the connection stays signed in. Your code gets an access token from Vercel Connect and sends it as a Bearer token to https://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 OpenClaw mcp.json:
OpenClaw’s tool dispatcher will then expose all nine Data Legion tools to the agent loop.

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 at https://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”
The AI assistant will automatically select the right tool based on your request.

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.
Claude, ChatGPT, Grok and Vercel each have their own entry; Codex signs in as ChatGPT and shares its entry. Any other assistant that signs in with your account appears under Other Apps, and those assistants share one key. If your account has more than one team, choose the team on the assistant’s entry, then call a tool again. Each connected assistant’s key also appears on the API Keys page, labeled Connected App. Removing a user from your account, or changing their role to one without access to API keys, disconnects their assistants.

Rate Limits

The same rate limits apply to MCP tool calls as to direct API calls.