Anchord MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANCHORD_API_KEY | Yes | Your Anchord API key (Bearer token) | |
| ANCHORD_API_BASE_URL | No | API base URL | https://api.anchord.ai |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_companyA | Resolve a company to an AnchorID using domain, name, city/state, or external identifiers. Returns status (resolved | needs_review | not_found), confidence score, the canonical AnchorID, match reasons, and any ambiguous candidates. |
| resolve_company_batchA | Resolve multiple companies to AnchorIDs in a single call (max 200). Each item needs a client_ref for correlation and at least one identifying field. Ambiguous matches return status needs_review with candidate AnchorIDs. |
| resolve_personA | Resolve a person to an AnchorID using email, name, company domain, or external identifiers (Slack/Google user IDs). Returns status (resolved | needs_review | not_found), confidence score, the canonical AnchorID, match reasons, and any ambiguous candidates. |
| resolve_person_batchA | Resolve multiple people to AnchorIDs in a single call (max 200). Each item needs a client_ref for correlation and at least one identifying field. Ambiguous matches return status needs_review with candidate AnchorIDs. |
| get_entityB | Fetch an AnchorID (canonical entity) by UUID. Optionally include linked source records via the include parameter (links, source_records, or both). |
| link_source_recordB | Create or reactivate a link between an AnchorID and a source record. Idempotent — calling twice returns the existing link. |
| unlink_source_recordA | Soft-delete the link between an AnchorID and a source record. Idempotent — calling on an already-unlinked pair returns 200. |
| guard_writeA | Evaluation-only pre-write safety check. Verifies the AnchorID exists, confidence meets threshold, no unresolved conflicts, and at least one canonical link is present. Returns allowed/blocked with reasons. This tool does NOT perform any write — the caller decides whether to proceed. |
| guard_write_batchA | Batch pre-write safety check for multiple AnchorIDs (max 200). Each item needs a client_ref for correlation. Returns per-item allowed/blocked decisions with reasons. Evaluation-only — never writes. |
| ingest_recordA | Ingest a single source record into Anchord. The record is matched to an AnchorID automatically. Requires a registered source (system). Wraps POST /ingest/batch with a single-item array. |
| get_entity_exportB | Export the golden record for an AnchorID. Returns the merged/canonical view of all linked source records as a single JSON object. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a distinct operation: entity retrieval, export, pre-write guards, ingest, linking/unlinking, and resolution for persons and companies. Batch variants are clearly separated from single-item counterparts, with no overlapping purposes.
All tools follow a consistent verb_noun pattern in snake_case (e.g., get_entity, guard_write, resolve_company_batch). The naming is predictable and easy to navigate.
With 11 tools, the set is well-scoped for an entity resolution and management server. Each tool serves a clear purpose, covering core workflows without unnecessary bloat or deficit.
The tool surface covers the essential lifecycle: resolution, ingestion, linking, pre-write guards, and retrieval. Minor gaps exist (no listing/search, no direct source record fetch, no entity update/delete), but the core functionality is well-supported.