Entity Enricher provides a hosted Model Context Protocol (MCP) server that connects AI assistants to its data tools. Codex, Cursor, VS Code with GitHub Copilot, Claude Code, and Claude can use it to author schemas, run single or batch enrichments, merge model results, and read saved records within a conversation.
The Model Context Protocol is the open standard that lets AI assistants call external tools. An MCP data enrichment server exposes enrichment operations as tools an agent can invoke: instead of you exporting a spreadsheet, running a pipeline, and importing results, you tell your assistant "enrich these 50 companies against my Company schema" and it orchestrates the work -- starting jobs, polling progress, and answering follow-up questions along the way.
Entity Enricher's MCP server is embedded in the platform itself -- the same engine behind the web app and REST API, with the same role-based permissions. Its tools and resources cover schema authoring, sample generation, single and batch enrichment, multi-model fusion, model benchmarks, and async job control.
Choosing how your agent builds a database? Compare agent-written SQL with EE's reviewed relationships and ongoing sync in the Supabase MCP product catalog example.
Generate a JSON schema from a sample or a description, refine it in natural language, and save it -- the same self-correcting generator as the web app.
Start one enrichment or a parallel batch, poll job status, cancel, retry failed expertise domains, and fetch the persisted records when done.
Run several LLMs on the same entity and merge the results -- conflicts are detected per field and resolved by rules or an LLM arbiter with recorded reasoning.
Chat-shaped by design: when pre-flight classification flags a mismatch ("Titan is a moon, not a planet"), the job pauses and your agent answers the question to resume -- no restart.
OAuth connects the client to an Entity Enricher account with the account's own role. Access can be revoked from API Keys → Connected Apps. Clients that use an API key send it in the X-API-Key header; the detailed guide includes that configuration as well.
These examples use browser sign-in (OAuth) and the same Streamable HTTP endpoint: https://entityenricher.ai/api/mcp/, including the trailing slash. Each client has its own configuration format.
Codex shares MCP settings between its app, CLI, and IDE extension through ~/.codex/config.toml. The first command registers Entity Enricher; the login command opens browser sign-in when authentication is needed.
codex mcp add entity-enricher --url https://entityenricher.ai/api/mcp/
codex mcp login entity-enricherCursor reads project servers from .cursor/mcp.json, or personal servers from ~/.cursor/mcp.json. The remote server entry uses mcpServers; Cursor handles the OAuth sign-in flow.
{
"mcpServers": {
"entity-enricher": {
"url": "https://entityenricher.ai/api/mcp/"
}
}
}VS Code uses .vscode/mcp.json with a servers object and an explicit http transport. Starting the server makes its tools available to GitHub Copilot's agent after authorization.
{
"servers": {
"entity-enricher": {
"type": "http",
"url": "https://entityenricher.ai/api/mcp/"
}
}
}This command registers a remote HTTP server in Claude Code. The /mcp command inside Claude Code opens its connection and authentication controls.
claude mcp add --transport http entity-enricher https://entityenricher.ai/api/mcp/On claude.ai and Claude Desktop, the Connectors settings offer an "Add custom connector" action. The connector takes the server URL above and opens Entity Enricher's authorization screen. This hosted connection is configured through Connectors; claude_desktop_config.json is for local servers.
API-key configuration, the complete tool reference, and recipe walkthroughs are in the MCP server documentation.
"List my Entity Enricher schemas, then enrich Sanofi using my pharmaceutical company schema and show the saved result."
Pasting rows into a chat gives you unvalidated text you still have to clean up. Going through the MCP server gives your agent the full platform: schema-validated output, multi-model cross-checking, semantic IDs that dedupe entities across runs, persisted records with cost tracking, and hallucination defenses -- while the conversation stays the control surface.
An Entity Enricher account gives Codex and other compatible clients access to the same schemas, enrichment tools, and saved records as the web application.
Get Started Free