
Entity Enricher
ai.entityenricherv2.0.0更新於 Oct 1, 2026
Multi-LLM entity enrichment: schemas, single/batch enrichment, fusion, model benchmarks.
概覽
託管式 MCP 伺服器,讓助理設計實體結構描述、以多個大型語言模型擴充實體、融合紀錄,並把結果同步到資料庫。
- 功能
- Entity Enricher 是託管式 MCP 伺服器,提供 58 個結構描述撰寫與實體擴充工具。助理可從樣本或文件產生並編輯可重用的結構描述,對單一實體或批次實體進行多語言、多模型擴充,重試失敗的專長領域,並把多筆紀錄融合為仲裁紀錄。它也涵蓋語意身分解析、基準情境、同步至 PostgreSQL、MySQL 或 SQLite 的資料庫同步,以及工作輪詢。
- 適用情境
- 當助理需要把非結構化或不完整的實體資料大規模轉成符合結構描述的結構化紀錄、在你自己的任務上比較模型,或把擴充後的實體資料列寫入關聯式資料庫時使用。它適合重複性的擴充流程,而非一次性查詢。
- 執行需求
- 遠端 Streamable HTTP 端點,無需本機安裝。支援 MCP 驗證規範的用戶端建議使用 OAuth 2.1 瀏覽器授權;否則透過 X-API-Key 標頭傳入組織存取金鑰,角色為 operator、editor 或 owner。選用的資料庫遞送需在你自己的複本主機上執行 ee-database 用戶端,其 DSN 保留在當地。擴充與基準測試會消耗計費額度。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Entity Enricher,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"enricher": {
"type": "http",
"url": "https://entityenricher.ai/api/mcp/"
}
}
}README
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 Code
Then run /mcp in a session and pick Authenticate — your browser opens the consent page.
More options (project .mcp.json, API-key fallback): examples/claude-code/
claude.ai
Settings → Connectors → Add custom connector with URL
https://entityenricher.ai/api/mcp/, then click Authorize on the consent screen.
Walkthrough: examples/claude-ai-remote.md
Cursor / other OAuth-capable clients
Register the URL with no headers and the client prompts you to sign in: examples/cursor/mcp.json
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.
-
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. -
For Claude Desktop, edit
~/Library/Application Support/Claude/claude_desktop_config.json(macOS) or%APPDATA%\Claude\claude_desktop_config.json(Windows):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:
Tool signatures are the callable contract. The wrappers share backend services, but do not expose every REST/UI option. Schema mutations require editor; benchmark mutations/runs require owner plus a benchmark-enabled plan. Database registration/credentials require owner plus a sync-enabled plan. See each tool for its requirements.
Data resources
Jobs and errors
Long-running work uses this server's start → poll → fetch interface. Start tools return a
job_id; generate_sample can already be paused or completed when it returns. Poll
get_job_status, answer paused questions through answer_job_question, and retrieve records
by list_records(job_id=...). A missing in-memory job is not proof of completion; check for
persisted records. Cancellation does not undo earlier records or database writes.
Most failures return success: false, error_code and message; some older tools return
only error or message. A successful MCP transport response does not imply successful
work. Inspect classification warnings, failed model legs, and partial/rejected database
outcomes even when an output is present. Detailed recovery is in the enrichment guide.
Scope and limitations
- The MCP single/batch enrichment tools do not expose web-search activation; sample generation does.
- Batch enrichment has no fixed 100-entity cap, but live quotas/credits can stop remaining work.
- The batch tool has no
database_sync=falseoption; the single-entity tool does. - Record deletion/restoration, detailed cost analytics, benchmark result import/export and some database administration remain in the web app or REST API.
- Schema documents use the supported JSON Schema dialect with Entity Enricher annotations; see the schema reference before authoring one directly.
Links
- Public MCP documentation
- REST API reference
- Client configurations
- MCP Registry —
ai.entityenricher/enricher; manifest: server.json
About this repository
This public repository contains documentation and client examples. The server is embedded in the Entity Enricher backend and maintained in the private monorepo; this directory is synced as a git subtree. Licensed under the MIT License.
來源:README.md,提交 663684e
工具
0版本歷史
1- v2.0.0最新Sep 16, 2026


