# Attio API + MCP vs Relaticle (slim)

> Attio scores 60.9 (C) to Relaticle's 59.6 (C) for crm records. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/attio-vs-relaticle.md (~3,500 tokens) · this version ~1,380 tokens · JSON https://www.anchorterminal.com/compare/attio-vs-relaticle.json · canonical https://www.anchorterminal.com/compare/attio-vs-relaticle
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Attio API + MCP scores 60.9 (C) on agent readiness against Relaticle's 59.6 (C), and leads in 2 of 7 scored categories. Relaticle leads on maintenance & community. Both do crm records.

- Attio API + MCP: C 60.9, rank #630 of 1486 · https://www.anchorterminal.com/tools/attio.min.md
- Relaticle: C 59.6, rank #694 of 1486 · https://www.anchorterminal.com/tools/relaticle.min.md
- Attio API + MCP, good for Small teams and startups that want an agent to search across records, notes, emails and calls and then update the CRM, starting free. Ahead on Reliability, 77 against 40.
- Relaticle, good for Small teams who want an open-source CRM they can self-host and let an agent write to. Ahead on Maintenance & community, 90 against 63. Also Open source; No incidents deducted, where Attio API + MCP loses 3 points for them.

| Category | Attio API + MCP | Relaticle |
| --- | --- | --- |
| Reliability (16%) | 77 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 82 | 86 |
| Agent ergonomics (13%) | 62 | 59 |
| Security & auth (14%) | 56 | 57 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 63 | 90 |
| Transparency & trust (7%) | 69 | 73 |

| Fact (where they differ) | Attio API + MCP | Relaticle |
| --- | --- | --- |
| Vendor | Attio | Relaticle, Inc. |
| Hosted endpoint | `https://api.attio.com/v2` | `https://mcp.relaticle.com` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Licence | none | AGPL-3.0 |
| Tools exposed | 48 | 50 |
| Read-only variant documented | no | yes |
| MCP registry | not listed | `com.relaticle/crm` |
| Last release | 2026-10-28 | 2026-11-05 |
| Terms last updated | 2025-11-01 | 2026-08-26 |
| Privacy policy last updated | 2026-06-01 | 2026-11-04 |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 9.9k npm/wk | 1.8k stars |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Reliability, Attio API + MCP +37: Attio API + MCP 77 (status.attio.com moved to incident.io, with five components and data back to August 2020 (20). Its feed and 90-day bars show four incidents from 4 August to 2 November 2026, all partial. On 8 September, "Platform avaliblity issues", intermittent availability problems on Attio Cloud and the web client from 17:05 to monitoring at 17:24 UTC. On 28 September workflow execution and webhook delivery ran late for about 4 hours. On 6 October formula updates and on 12 October bulk record deletions were delayed on Background Tasks. Minor incidents only (20). Rate limits published, 100 reads and 25 writes a second, plus score-based limits on list queries in a 10-second window (15). 429s carry a Retry-After date and a JSON body, and the docs say rate-limited requests weren't processed and can be retried. Upsert (assert) endpoints give a safe retry for creates, but there's no idempotency key (12 of 15). No SLA found on the pricing page (0). REST v2 and the MCP server carry no beta label, though several newer endpoints do (10). 20 + 20 + 15 + 12 + 0 + 10 = 77.); Relaticle 40 (Graded with the hosted lines on Relaticle Cloud's REST API and MCP server, the surface an outside agent calls; the software also self-hosts. No status page is linked and status.relaticle.com did not connect (0). With no readable history the incident line scores 5. Limits have numbers: 600 a minute per workspace and 300 reads or 60 writes a minute per token in the source, and 120 MCP calls a minute per user in the docs (15). 429 is in the OpenAPI responses and upserts by unique field give a safe retry for creates, but the backoff guidance sits on a docs section we read only as a heading (10 of 15). No SLA (0). Version 3.8, not labelled beta (10). 0 + 5 + 15 + 10 + 0 + 10 = 40.)
- Maintenance & community, Relaticle +27: Attio API + MCP 63 (REST changelog entries on 28 October (writable `avatar_url` and `logo_url`), 27 October, 15 October and 14 October 2026, and MCP entries on 14 October and 1 October (30). Seventeen dated entries (13 REST, 4 MCP) across the REST and MCP changelogs since 4 August 2026 (20). Closed service with public changelogs and a support address. We didn't test support (10 of 15). Not in the official MCP registry. A search for attio on 2 November returns only third-party servers (kesslerio, kaszek, Smithery). No official REST SDK (0). The only npm package is the App SDK CLI, version not re-read (3 of 10). 30 + 20 + 10 + 0 + 3 = 63.); Relaticle 90 (v3.8.2 tagged on 5 November 2026 and commits on 6 November (30). Thirteen tags between 9 October and 5 November alone (20). More than 2,500 commits since 1 August and merged pull requests numbered past 1,100; the GitHub API did not answer, so open issues and reply times were not counted (15 of 25). Verified com.relaticle/crm namespace in the official MCP registry with the hosted remote (15). CI, tests, security-audit and Dependabot workflows, PHP 8.5 and Laravel 13 (10). 30 + 20 + 15 + 15 + 10 = 90.)