Troubleshooting the Tamr MCP Server
Check the troubleshooting table for likely causes and resolutions for common problems.
| Problem | Suggested Resolution |
|---|---|
| 401 / authentication errors (API key) | Check that the Authorization: Bearer apk_... header is present and that the key is valid for the tenant. |
| 401 / authentication errors (OAuth) | The session might have expired. Sign in again. |
| 403 after OAuth sign-in | Your account must belong to the organization for the tenant. Sign in with an account from that tenant. |
| Connection refused or host errors | Confirm that the tenant URL matches your Tamr Cloud domain exactly (https://<your-tenant>.tamr.cloud), including the /mcp path (https://<your-tenant>.tamr.cloud/mpc). |
| Tools do not appear after setup | Fully restart the client (not just reconnect) after editing its config. For Claude Desktop, confirm |
tamr_list_tables shows only some tables | Without a project_id, Tamr returns one page per project. Follow each entry in projectsWithMore, and check projectsFailed for projects that could not be read. |
tamr_search returns "unknown_fields" | Searchable fields are table-specific. Call tamr_describe_table and use the exact field names it returns. |
tamr_find_records returns no results | Matching is exact. Check the field name and the value's case, whitespace, and type (for example, "US" does not match "us", and 5 does not match "5"). If it returns |
| A suggested edit or merge is not applied to the record | tamr_suggest_edit and tamr_suggest_duplicate only submit items to a curation queue; they never directly change the record.A data steward must apply the item using tamr_close_queue_item (or in the Tamr UI) to apply the suggested edit or merge. |
Updated about 2 hours ago
Did this page help you?