Entity Enricher MCP Server

A hosted Model Context Protocol server for Entity Enricher, available at https://entityenricher.ai/api/mcp/ (Streamable HTTP).

From an MCP-compatible client you can:

• Design reusable schemas from sample data or documents and edit properties directly.
• Enrich single entities or lists, with multilingual fields and multiple models.
• Fuse results and recover failed expertise domains without repeating successful work.
• Resolve recurring objects to semantic identities and curate their aliases or uncertain matches.
• Derive relational tables and migrations for your PostgreSQL, MySQL or SQLite database.
• Benchmark enrichment, sample generation and schema generation on your own tasks.

Schema validation and model agreement do not establish factual truth or freshness. Inspect the actual sources, failures and partial outcomes. A successful generation, entity-layer admission and application on your external replica are distinct outcomes.

The MCP server needs no local installation. Optional database delivery uses ee-database on your replica host; its DSN stays there. Managed hosts can provision automatically; manual pairing is also supported.

Quickstart

Option 1 — OAuth (recommended)

For claude.ai, Claude Code, Cursor, and any MCP client that implements the standard OAuth flow. No API key to create or paste — the client discovers the authorization server automatically, your browser opens the Entity Enricher consent screen, and the connection acts on your behalf with your own role. Revoke it anytime under Settings → API Keys → Connected Apps.

claude mcp add --transport http entity-enricher https://entityenricher.ai/api/mcp/

Option 2 — API key (static JSON configuration)

For clients configured via a JSON file rather than an interactive sign-in (Claude Desktop, Continue, Zed) — and for headless/CI use.

1. In the Entity Enricher web UI: Settings → API Keys → New organization access key. Pick a role — operator (read-mostly), editor (create/edit schemas), or owner (full control, required for benchmarks). Copy the ent_… value; it's only shown once.

2. For Claude Desktop, edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

   config.json

   Copy

   {
     "mcpServers": {
       "entity-enricher": {
         "url": "https://entityenricher.ai/api/mcp/",
         "headers": { "X-API-Key": "ent_your_key_here" }
       }
     }
   }
   

   Restart Claude Desktop. Full file: examples/claude-desktop/

Try it

List my Entity Enricher schemas, then enrich "Sanofi" against the pharmaceutical company schema in English and French.

The client discovers the tools, reads the selected schema and returns the result with a link. Automatic model selection is available; consequential choices are reviewed when needed.

Guides and tool descriptions

Server instructions explain the workflows. Tool descriptions explain individual calls, including preconditions, costs and consequential effects. Detailed modeling, recovery and migration guidance is loaded only when needed.

Use MCP resources/list to discover the guide index (enricher://docs) and each guide, then resources/read on the desired URI. Guides do not run a model. Clients decide how resources enter model context; reading them is not guaranteed to be token-free.

The following public recipes are generated from the same packaged Markdown the server serves. Edit the source guides in the main repository, not these generated copies.

If a client cannot read MCP resources, use these public links. The guides complement individual tool contracts; ordinary calls do not require reading them all.

Tools

58 tools, spanning the full schema-authoring and enrichment surface: