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
The MCP server uses the sameAPI-Key authentication as the REST API. Pass your API key in the headers section of your MCP client configuration. The key is forwarded to the API on every tool call, so credits and rate limits apply exactly as they do for direct API calls.
Setup
Claude Code
Add to your project’s.mcp.json:
Claude Desktop
Add to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
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 a Custom GPT or workspace with MCP enabled, add a connector pointing athttps://api.datalegion.ai/mcp. Set authentication to Custom header with header name API-Key and your key as the value. ChatGPT will discover the seven Data Legion tools and call them automatically.
Gemini (Gemini CLI / Code Assist)
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 7 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
| Tool | Description | API Equivalent |
|---|---|---|
person_enrich | Look up a person by email, phone, name, LinkedIn, or other identifiers | POST /person/enrich |
person_search | Query people using SQL WHERE syntax | POST /person/search |
Company
| Tool | Description | API Equivalent |
|---|---|---|
company_enrich | Look up a company by domain, name, ticker, or LinkedIn | POST /company/enrich |
company_search | Query companies using SQL WHERE syntax | POST /company/search |
Utilities
| Tool | Description | API Equivalent |
|---|---|---|
utility_clean | Normalize emails, phones, names, domains, and other fields | POST /utility/clean |
utility_hash_email | Hash an email address (SHA-256, SHA-1, MD5) for privacy-safe lookups | POST /utility/hash/email |
utility_validate | Validate data format and get cleaning suggestions | POST /utility/validate |
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”