{ "data": { "a": { "slug": "close", "name": "Close API + MCP", "vendor": "Close", "vendorUrl": "https://www.close.com", "kind": "http-api", "category": "crm", "summary": "REST API and hosted MCP server for Close, a sales CRM built around calling, email and SMS.", "url": "https://www.anchorterminal.com/tools/close", "markdownUrl": "https://www.anchorterminal.com/tools/close.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/close.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/close.json", "dns": "close.grade.anchorterminal.com", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.close.com/api/v1", "packages": [ { "registry": "pypi", "name": "closeio" } ], "auth": "mixed", "authNotes": "API keys over HTTP Basic (key as username, empty password), scoped to one user and organisation; OAuth 2.0 for apps. The hosted MCP server at https://mcp.close.com/mcp takes OAuth with dynamic client registration, or the headers Close-API-Key plus Close-Scope set to mcp.read, mcp.write_safe or mcp.write_destructive.", "pricing": "paid", "pricingNotes": "No free plan, a 14-day trial with no card. Solo $9 a seat a month billed yearly or $19 monthly, Essentials $35 or $49, Growth $99 or $109, Scale $139 or $149. API access is on every plan. Calls around $0.02 a minute and SMS at cost on top (https://www.close.com/pricing).", "priceSummary": "$9 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No payments. Access follows the Close subscription.", "endpoints": [] }, "toolCount": 141, "popularity": { "githubStars": 70, "npmWeekly": null, "pypiWeekly": 13891, "asOf": "2026-09-30" }, "docsUrl": "https://developer.close.com", "llmsTxt": "https://developer.close.com/llms.txt", "openapi": "https://api.close.com/api/openapi.json", "registryName": "com.close/close-mcp", "capabilities": [ "crm.records", "crm.pipeline", "crm.activities", "crm.search", "crm.webhooks", "crm.email" ], "tags": [ "hosted", "mcp", "llms-txt", "openapi", "webhooks", "closed-source", "no-card", "python", "read-only-mode" ], "lastRelease": "2026-09-10", "graded": true, "anchor": { "graded": true, "score": 56.2, "grade": "C", "agentReady": false, "rank": 836, "ranked": true, "rankOf": 1486, "categoryRank": 11, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 49, "payments": 30, "reliability": 56, "schema": 82, "security": 66, "transparency": 68 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": -3, "negativeNotes": [ "-3. A published behaviour changed for existing clients, announced the day it took effect. The 16 July 2026 changelog entry says creating a membership through the API \"now requires\" the organisation to have domain restriction enabled and the new member's email on a verified domain, with no earlier notice found. https://developer.close.com/api/overview/changelog/2026/7/16" ], "verdict": "Three MCP scopes chosen per connection limit an agent to 80 read tools or 99 with creates, and email tools only save drafts. The full set is 141 tools. The API was down across regions for about 2.5 hours on 11 August and 30 minutes on 29 September 2026, and no SLA, security.txt or bug bounty was found.", "bestFor": "Inside-sales teams that call, email and text from the CRM and want an agent to log, triage and draft without being able to send or delete by default.", "strengths": [ "Three MCP scopes chosen per connection, read (80 tools), safe write (99) and destructive (141)", "Email tools create drafts only, never send", "Delete tools tell the model the action cannot be undone and to act only on an explicit instruction", "`RateLimit` header on every response and `retry-after` on every 429", "Event log API on every plan, and SOC 2 Type 2" ], "weaknesses": [ "141 MCP tools, and even the read scope loads 80", "Two outages reached the API in the 90 days to 1 November 2026, on 11 August and 29 September", "OAuth for REST apps has a single full-access scope", "No public subprocessor list, no security.txt and no bug bounty found", "One dated API changelog entry since 3 August 2026, and no free plan, only a 14-day trial" ], "agentNotes": [ "Connect with `Close-Scope: mcp.read` unless the job needs writes, and `mcp.write_safe` if it only creates", "Sleep for the `reset` value in the `RateLimit` header after a 429, which the docs say beats `retry-after`", "Use cursors through advanced filtering or the event log for large pulls, since `_skip` has a per-resource ceiling", "Search the lead before `create_lead`, because there's no idempotency key and a retry makes a duplicate", "Expect `create_draft_email` to leave a draft, and tell the user to send it from Close" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 56.2 } ], "editorialScores": { "ergonomics": 56, "maintenance": 49, "payments": 30, "reliability": 56, "schema": 82, "security": 66, "transparency": 47 }, "provenanceScore": 89, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.close.com/api/v1/me/ -u \"$CLOSE_API_KEY:\"", "claudeCode": "claude mcp add --transport http close https://mcp.close.com/mcp --header \"Close-API-Key: $CLOSE_API_KEY\" --header \"Close-Scope: mcp.read\"", "config": { "mcpServers": { "close": { "url": "https://mcp.close.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/crm.records", "tool": "https://letme.dev/close" }, "area": "business", "unitPrices": [ { "item": "Solo", "unit": "seat-month", "usd": 9, "note": "billed yearly, $19 monthly; API on every plan" }, { "item": "Essentials", "unit": "seat-month", "usd": 35, "note": "billed yearly, $49 monthly" }, { "item": "Growth", "unit": "seat-month", "usd": 99, "note": "billed yearly, $109 monthly" }, { "item": "Scale", "unit": "seat-month", "usd": 139, "note": "billed yearly, $149 monthly" }, { "item": "Outbound calls", "unit": "call-minute", "usd": 0.02, "note": "approximate, most destinations" } ], "provenance": { "legalEntity": "Elastic Inc", "domain": "close.com", "domainRegistered": "1996-02-20", "domainNote": "close.com was registered in 1996, long before the Close product took the name.", "endpointOnVendorDomain": true, "terms": "https://close.com/tos", "privacy": "https://close.com/privacy", "statusPage": "https://status.close.com", "changelog": "https://developer.close.com/api/overview/changelog", "securityTxt": "none", "checked": "2026-11-01", "score": 89 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/close.json", "live": { "slug": "close", "probe": { "target": "https://api.close.com/api/v1", "method": "get", "lastAt": "2026-11-07T18:20:17.612451198Z", "lastOk": true, "lastStatus": 404, "lastMs": 548, "authRequired": false, "uptime24h": 100, "uptime30d": 99.99, "p50ms24h": 458, "p95ms24h": 571, "samples24h": 239, "samples30d": 7910, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 251 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 248, "ok": 248 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.close.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:20:41.690211173Z" }, "versions": [ { "registry": "mcp-registry", "name": "com.close/close-mcp", "version": "1.0.1", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "pypi", "name": "closeio", "version": "2.1", "released": "2023-07-25", "seenAt": "2026-11-06T23:15:27.08852058Z" } ], "pypiWeekly": 10280, "securityTxt": { "url": "https://close.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:24.484554452Z" }, "llmsTxt": { "url": "https://developer.close.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:51.196167239Z" }, "domain": { "domain": "close.com", "registered": "1996-02-20", "source": "https://rdap.verisign.com/com/v1/domain/close.com", "checkedAt": "2026-11-01T14:26:54.039936881Z" }, "pages": [ { "url": "https://developer.close.com/api/overview/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:03:01.683922952Z", "changedAt": "2026-11-06T13:25:36.871748809Z", "fingerprint": "72607f52a907" }, { "url": "https://www.close.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:26:53.021075164Z", "changedAt": "2026-10-31T06:26:01.324876182Z", "fingerprint": "29d00f263281" }, { "url": "https://close.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:01:09.162421361Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "af850e65f4fd" }, { "url": "https://close.com/tos", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:01:11.46444464Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "8f7850d129a1" } ], "mcpTools": { "url": "https://mcp.close.com/mcp", "checkedAt": "2026-11-07T01:43:15.089972228Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:43:15.089972228Z" }, "updatedAt": "2026-11-07T18:20:17.612451198Z" } }, "answer": "Relaticle scores 59.6 (C) on agent readiness against Close API + MCP's 56.2 (C), and leads in 4 of 7 scored categories. Close API + MCP leads on reliability and security \u0026 auth.", "b": { "slug": "relaticle", "name": "Relaticle", "vendor": "Relaticle, Inc.", "vendorUrl": "https://relaticle.com", "kind": "http-api", "category": "crm", "summary": "Relaticle is an open-source CRM under AGPL-3.0 for companies, people, opportunities, tasks and notes, run on Relaticle Cloud or self-hosted. Agents use its REST API and an MCP server with OAuth or scoped tokens.", "url": "https://www.anchorterminal.com/tools/relaticle", "markdownUrl": "https://www.anchorterminal.com/tools/relaticle.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/relaticle.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/relaticle.json", "dns": "relaticle.grade.anchorterminal.com", "repo": "https://github.com/relaticle/relaticle", "license": "AGPL-3.0", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.relaticle.com", "packages": [], "auth": "mixed", "authNotes": "Personal access tokens from Settings \u003e Access Tokens are tied to one workspace, take an expiry and carry chosen permissions (read, create, update, delete for REST, plus read, draft and send email for MCP). MCP clients can also use OAuth 2.1 through Laravel Passport and choose one workspace on the consent screen; the source says the OAuth scope `mcp:use` authorises the whole toolset.", "pricing": "freemium", "pricingNotes": "Self-hosting is free under AGPL-3.0. Relaticle Cloud is priced per workspace with unlimited users: Cloud Pro $19 a month billed yearly ($24 monthly) and Cloud Scale $49 ($59 monthly), Enterprise from $20,000 a year. A 14-day Cloud Pro trial needs no card. Scale has three times the API and MCP throughput.", "priceSummary": "$19 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the OpenAPI spec, the developer docs or the source (checked 2026-11-06). Over-limit Cloud calls return 402 for plan limits without payment requirements.", "endpoints": [] }, "toolCount": 50, "popularity": { "githubStars": 1811, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://relaticle.com/developers/rest-api", "llmsTxt": "https://relaticle.com/llms.txt", "openapi": "https://relaticle.com/openapi.json", "registryName": "com.relaticle/crm", "capabilities": [ "crm.records", "crm.pipeline", "crm.activities", "crm.search", "email.send", "email.threads" ], "tags": [ "official", "open-source", "agpl", "self-hosted", "hosted", "mcp", "remote-mcp", "mcp-registry", "oauth", "openapi", "llms-txt", "freemium", "trial", "no-card", "php", "eu-hosting" ], "lastRelease": "2026-11-05", "graded": true, "anchor": { "graded": true, "score": 59.6, "grade": "C", "agentReady": false, "rank": 694, "ranked": true, "rankOf": 1486, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 59, "maintenance": 90, "payments": 30, "reliability": 40, "schema": 86, "security": 57, "transparency": 73 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Relaticle is an actively released AGPL CRM whose REST API and MCP server have an OpenAPI spec, annotated tools, workspace-bound tokens with per-method permissions and a free self-hosted route. MCP writes apply at once with no server-side confirmation, OAuth grants the whole toolset, and Cloud has no status page, SLA or certification.", "bestFor": "Small teams who want an open-source CRM they can self-host and let an agent write to.", "strengths": [ "AGPL-3.0 source, free to self-host, with tagged releases about twice a week", "Tokens are bound to one workspace with an expiry and per-method permissions, so a read-only token is possible", "OpenAPI 3.1 spec, llms.txt and MCP tools with readOnly, destructive and idempotent hints", "Filter grammar with $and, $or and $not, cursor paging and upserts by unique field", "Cloud providers listed with what each receives, hosting at Hetzner in Germany" ], "weaknesses": [ "Writes over MCP apply immediately, and OAuth's single `mcp:use` scope authorises every tool", "No status page or SLA for Relaticle Cloud was found", "No SOC 2 or ISO 27001, which the security page says plainly", "No changelog page beyond GitHub tags, and no deprecation policy", "50 MCP tools by default, with no toolsets or read-only subset" ], "agentNotes": [ "Use a personal access token with only the read permission unless the task writes, since OAuth grants every tool", "Ask the user before create, update, delete or send tools; the server applies them at once", "Call `get-crm-schema-tool` for an entity before filtering on custom fields, which differ by workspace", "Use `POST /v1/people/upsert` or `/v1/companies/upsert` with a unique field to avoid duplicates on retry", "Keep MCP calls under 120 a minute per user and REST writes under 60 a minute per token on Cloud Pro" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59.6 } ], "editorialScores": { "ergonomics": 59, "maintenance": 90, "payments": 30, "reliability": 40, "schema": 86, "security": 57, "transparency": 72 }, "provenanceScore": 74, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.relaticle.com/v1/companies -H \"Authorization: Bearer YOUR_TOKEN\" -H \"Accept: application/json\"", "claudeCode": "claude mcp add --transport http relaticle https://mcp.relaticle.com", "config": { "mcpServers": { "relaticle": { "url": "https://mcp.relaticle.com" } } } }, "letme": { "capability": "https://letme.dev/crm.records", "tool": "https://letme.dev/relaticle" }, "area": "business", "unitPrices": [ { "item": "Cloud Pro workspace", "unit": "month", "usd": 19, "note": "Billed yearly at $228; $24 billed monthly" }, { "item": "Cloud Scale workspace", "unit": "month", "usd": 49, "note": "Billed yearly at $588; $59 billed monthly" } ], "provenance": { "legalEntity": "Relaticle, Inc.", "domain": "relaticle.com", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://relaticle.com/terms-of-service", "privacy": "https://relaticle.com/privacy-policy", "statusPage": "", "changelog": "https://github.com/relaticle/relaticle/releases", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "Terms of service effective 26 August 2026 and privacy policy effective 4 November 2026; the footer names Relaticle, Inc. No clause on automated access to the website was found.", "relaticle.com/robots.txt allows all crawlers and names ClaudeBot as allowed.", "security.txt names security@relaticle.com and expires 6 May 2027. The security page asks for reports by email and aims to acknowledge within 48 hours.", "status.relaticle.com did not connect and no status page is linked. relaticle.com/changelog is 404; releases are tagged on GitHub.", "The press page says Relaticle was founded in 2024 and lists 1,811 GitHub stars, verified 26 September 2026. Domain registration date not checked." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/relaticle.json", "live": { "slug": "relaticle", "probe": { "target": "https://mcp.relaticle.com", "method": "get", "lastAt": "2026-11-07T18:20:50.642634031Z", "lastOk": true, "lastStatus": 405, "lastMs": 234, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 174, "p95ms24h": 292, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "versions": [ { "registry": "github", "name": "relaticle/relaticle", "version": "v3.8.2", "released": "2026-11-04", "seenAt": "2026-11-07T00:00:54.651079547Z" }, { "registry": "mcp-registry", "name": "com.relaticle/crm", "version": "3.8.2", "seenAt": "2026-11-07T18:16:28.95801333Z" } ], "githubStars": 1811, "securityTxt": { "url": "https://relaticle.com/.well-known/security.txt", "state": "valid", "expires": "2027-05-07T16:01:18Z", "checkedAt": "2026-11-07T16:01:18.554359358Z" }, "llmsTxt": { "url": "https://relaticle.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:44.579905089Z" }, "pages": [ { "url": "https://relaticle.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:18:13.002922035Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6e701d3eab86" }, { "url": "https://relaticle.com/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:18:15.26331735Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1e5fff279d1d" } ], "mcpTools": { "url": "https://mcp.relaticle.com", "checkedAt": "2026-11-07T01:47:13.278550358Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:47:13.278550358Z" }, "updatedAt": "2026-11-07T18:20:50.642634031Z" } }, "edges": [ { "by": 41, "category": "maintenance", "leads": "relaticle", "name": "Maintenance \u0026 community", "reasons": { "a": "Newest changelog entry on 10 September 2026, 52 days before 1 November (20). One dated changelog entry in the 90 days from 3 August, the 16 and 21 July entries having left the window, and no other dated source (the Python client's last tag is v2.1 from July 2023 and the MCP registry entry is 1.0.1 from 22 September 2025), so fewer than three (0). Public changelog and support by email and phone. We didn't test support (10 of 15). In the official MCP registry as com.close/close-mcp, last version 1.0.1 published on 22 September 2025 (15). The Python client's CI was updated on 10 June 2026 (4 of 10). 20 + 0 + 10 + 15 + 4 = 49.", "b": "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." }, "scores": { "a": 49, "b": 90 } }, { "by": 16, "category": "reliability", "leads": "close", "name": "Reliability", "reasons": { "a": "Statuspage at status.close.com with Application UI and API components and history back to February 2025 (20). In the 90 days from 3 August, read from history.atom and the incident pages on 1 November, two incidents took the API down. On 11 August Close was intermittently unavailable for about 2.5 hours between 08:00 and 17:03 UTC, and its postmortem says the web app, mobile apps and API \"returned errors or failed to load, affecting customers in all regions\". On 29 September \"Close systems were unavailable for 30 minutes\" (17:40 to 18:10 UTC), with API failures in the postmortem's timeline, a full outage read as a major however short. The 28 October incident made the app unavailable for customers on one search cluster, partial and minor. Two majors (5). The 1 October check found nothing after 3 July. Limits are set per endpoint group, per key and per organisation (3 times the key limit), but the docs only give 20 a second as an example rather than a table (10 of 15). Every response carries a `RateLimit` header, and every 429 has both `RateLimit` and `retry-after`, with guidance to sleep for the reset value. No idempotency keys or safe-retry guidance for writes (11 of 15). No SLA found on the pricing page (0). REST and MCP carry no beta label (10). 20 + 5 + 10 + 11 + 0 + 10 = 56.", "b": "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." }, "scores": { "a": 56, "b": 40 } }, { "by": 9, "category": "security", "leads": "close", "name": "Security \u0026 auth", "reasons": { "a": "REST keys act as one user in one organisation over HTTP Basic and can be deleted. OAuth for apps has only `all.full_access` plus `offline_access`, with 1-hour access tokens and a revoke endpoint. The MCP server adds three scopes, `mcp.read`, `mcp.write_safe` and `mcp.write_destructive`, over OAuth with dynamic client registration or a key header (24 of 30). A read-only MCP connection is one header. Safe-write can create but not update or delete. Email tools only make drafts a person sends, and delete tools tell the model to act only on an explicit instruction (18 of 20). The MCP server reads emails, SMS and call transcripts written by outsiders, and we found no injection guidance. Draft-only email closes one exfiltration route (4 of 15). The event log API records changes and is on every plan (12 of 15). SOC 2 Type 2 on the security page. No security.txt (404 on 1 November), and no disclosure policy or bug bounty found (8 of 20). 24 + 18 + 4 + 12 + 8 = 66.", "b": "Personal access tokens are bound to one workspace, take an expiry and per-method permissions (read, create, update, delete, plus read, draft and send email), and travel in headers. OAuth 2.1 through Passport is also offered, but the source says its single `mcp:use` scope authorises the whole toolset (25 of 30). A read-only token is possible; the docs say MCP writes apply immediately and leave confirmation to the client (10 of 20). Synced email reaches the model through the email tools, and no prompt-injection guidance was found (0). Each record has an activity log of field changes and who made them, and admins see it across the workspace (12 of 15). security.txt valid to May 2027, a disclosure address with a 48-hour acknowledgement target and security-audit workflows in CI; the security page says there is no SOC 2 or ISO 27001 (10 of 20). 25 + 10 + 0 + 12 + 10 = 57." }, "scores": { "a": 66, "b": 57 } }, { "by": 5, "category": "transparency", "leads": "relaticle", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service with terms and a privacy policy, run by Elastic Inc (15). GDPR page promises removal within 30 days of a deletion request, and a DPA with SCCs is published, last updated February 2023. Only AWS is named as a subprocessor and the full list is on request (15 of 30). Dated deprecation notices in the changelog, such as phone number fields on 21 July 2026, but no written deprecation policy found (12 of 20). No public subprocessor list or hosting region found (5 of 20). 15 + 15 + 12 + 5 = 47. The privacy, GDPR and DPA pages rest on the 1 October check.", "b": "AGPL-3.0 source with an integration exception, and terms for the Cloud service (30). The privacy policy (4 November 2026) gives retention for server logs (90 days), contact forms (12 months) and paused trial workspaces (deleted after 60 days with notice), and names provider categories; no DPA was found (20 of 30). No deprecation policy or dated notices found (5 of 20). The security page lists each Cloud provider and what it receives, with hosting at Hetzner in Germany, and website analytics through Fathom without CRM content (17 of 20). 30 + 20 + 5 + 17 = 72." }, "scores": { "a": 68, "b": 73 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Close", "b": "Relaticle, Inc.", "name": "Vendor" }, { "a": "https://api.close.com/api/v1", "b": "https://mcp.relaticle.com", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "AGPL-3.0", "name": "Licence" }, { "a": "141", "b": "50", "name": "Tools exposed" }, { "a": "yes", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "com.close/close-mcp", "b": "com.relaticle/crm", "name": "MCP registry" }, { "a": "2026-09-10", "b": "2026-11-05", "name": "Last release" }, { "a": "2025-10-31", "b": "2026-08-26", "name": "Terms last updated" }, { "a": "2026-05-30", "b": "2026-11-04", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "70 stars, 14k PyPI/wk", "b": "1.8k stars", "name": "Popularity" }, { "a": "3.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Relaticle scores 59.6 (C) on agent readiness against Close API + MCP's 56.2 (C), and leads in 4 of 7 scored categories. Close API + MCP leads on reliability and security \u0026 auth.", "question": "Which is better for AI agents, Close API + MCP or Relaticle?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Close API + MCP and Relaticle need an API key?" }, { "answer": "Yes. Close API + MCP has a hosted endpoint at https://api.close.com/api/v1 and Relaticle at https://mcp.relaticle.com.", "question": "Can an agent call Close API + MCP and Relaticle without installing anything?" }, { "answer": "No open-source release is listed for Close API + MCP. Relaticle is open source (AGPL-3.0).", "question": "Are Close API + MCP and Relaticle open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 56 against 40", "Security \u0026 auth, 66 against 57" ], "also": null, "goodFor": "Inside-sales teams that call, email and text from the CRM and want an agent to log, triage and draft without being able to send or delete by default.", "slug": "close", "watchFor": "141 MCP tools, and even the read scope loads 80" }, { "aheadOn": [ "Maintenance \u0026 community, 90 against 49", "Transparency \u0026 trust, 73 against 68" ], "also": [ "Open source", "No incidents deducted, where Close API + MCP loses 3 points for them" ], "goodFor": "Small teams who want an open-source CRM they can self-host and let an agent write to.", "slug": "relaticle", "watchFor": "Writes over MCP apply immediately, and OAuth's single `mcp:use` scope authorises every tool" } ], "history": { "close": [ { "causes": [ "reliability", "event", "time" ], "date": "2026-11-01", "delta": -10.6, "from": 66.8, "fromGrade": "B", "to": 56.2, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 66.7, "fromGrade": "B", "to": 66.8, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.2, "from": 66.9, "fromGrade": "B", "to": 66.7, "toGrade": "B" } ], "relaticle": null }, "job": { "capability": "crm.records", "name": "CRM records" }, "others": [ { "json": "https://www.anchorterminal.com/compare/affinity-vs-close.json", "title": "Affinity vs Close API + MCP", "url": "https://www.anchorterminal.com/compare/affinity-vs-close" }, { "json": "https://www.anchorterminal.com/compare/affinity-vs-relaticle.json", "title": "Affinity vs Relaticle", "url": "https://www.anchorterminal.com/compare/affinity-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/attio-vs-close.json", "title": "Attio API + MCP vs Close API + MCP", "url": "https://www.anchorterminal.com/compare/attio-vs-close" }, { "json": "https://www.anchorterminal.com/compare/attio-vs-relaticle.json", "title": "Attio API + MCP vs Relaticle", "url": "https://www.anchorterminal.com/compare/attio-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/breakcold-vs-close.json", "title": "Breakcold vs Close API + MCP", "url": "https://www.anchorterminal.com/compare/breakcold-vs-close" }, { "json": "https://www.anchorterminal.com/compare/breakcold-vs-relaticle.json", "title": "Breakcold vs Relaticle", "url": "https://www.anchorterminal.com/compare/breakcold-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/capsule-crm-vs-close.json", "title": "Capsule CRM vs Close API + MCP", "url": "https://www.anchorterminal.com/compare/capsule-crm-vs-close" }, { "json": "https://www.anchorterminal.com/compare/capsule-crm-vs-relaticle.json", "title": "Capsule CRM vs Relaticle", "url": "https://www.anchorterminal.com/compare/capsule-crm-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/close-vs-copper.json", "title": "Close API + MCP vs Copper API", "url": "https://www.anchorterminal.com/compare/close-vs-copper" }, { "json": "https://www.anchorterminal.com/compare/close-vs-dynamics-365-sales.json", "title": "Close API + MCP vs Microsoft Dynamics 365 Sales", "url": "https://www.anchorterminal.com/compare/close-vs-dynamics-365-sales" }, { "json": "https://www.anchorterminal.com/compare/close-vs-folk.json", "title": "Close API + MCP vs folk API + MCP", "url": "https://www.anchorterminal.com/compare/close-vs-folk" }, { "json": "https://www.anchorterminal.com/compare/close-vs-freshsales.json", "title": "Close API + MCP vs Freshsales API", "url": "https://www.anchorterminal.com/compare/close-vs-freshsales" }, { "json": "https://www.anchorterminal.com/compare/close-vs-hubspot-mcp.json", "title": "Close API + MCP vs HubSpot API + MCP", "url": "https://www.anchorterminal.com/compare/close-vs-hubspot-mcp" }, { "json": "https://www.anchorterminal.com/compare/close-vs-nutshell.json", "title": "Close API + MCP vs Nutshell", "url": "https://www.anchorterminal.com/compare/close-vs-nutshell" }, { "json": "https://www.anchorterminal.com/compare/close-vs-payani-ai.json", "title": "Close API + MCP vs Payani AI", "url": "https://www.anchorterminal.com/compare/close-vs-payani-ai" }, { "json": "https://www.anchorterminal.com/compare/close-vs-pipedrive.json", "title": "Close API + MCP vs Pipedrive API + MCP", "url": "https://www.anchorterminal.com/compare/close-vs-pipedrive" }, { "json": "https://www.anchorterminal.com/compare/close-vs-salesflare.json", "title": "Close API + MCP vs Salesflare", "url": "https://www.anchorterminal.com/compare/close-vs-salesflare" }, { "json": "https://www.anchorterminal.com/compare/close-vs-salesforce.json", "title": "Close API + MCP vs Salesforce API + MCP", "url": "https://www.anchorterminal.com/compare/close-vs-salesforce" }, { "json": "https://www.anchorterminal.com/compare/close-vs-streak.json", "title": "Close API + MCP vs Streak API + MCP", "url": "https://www.anchorterminal.com/compare/close-vs-streak" }, { "json": "https://www.anchorterminal.com/compare/close-vs-sugarcrm.json", "title": "Close API + MCP vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/close-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/close-vs-twenty.json", "title": "Close API + MCP vs Twenty API + MCP", "url": "https://www.anchorterminal.com/compare/close-vs-twenty" }, { "json": "https://www.anchorterminal.com/compare/close-vs-zoho-crm.json", "title": "Close API + MCP vs Zoho CRM", "url": "https://www.anchorterminal.com/compare/close-vs-zoho-crm" }, { "json": "https://www.anchorterminal.com/compare/copper-vs-relaticle.json", "title": "Copper API vs Relaticle", "url": "https://www.anchorterminal.com/compare/copper-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/dynamics-365-sales-vs-relaticle.json", "title": "Microsoft Dynamics 365 Sales vs Relaticle", "url": "https://www.anchorterminal.com/compare/dynamics-365-sales-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/folk-vs-relaticle.json", "title": "folk API + MCP vs Relaticle", "url": "https://www.anchorterminal.com/compare/folk-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/freshsales-vs-relaticle.json", "title": "Freshsales API vs Relaticle", "url": "https://www.anchorterminal.com/compare/freshsales-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/hubspot-mcp-vs-relaticle.json", "title": "HubSpot API + MCP vs Relaticle", "url": "https://www.anchorterminal.com/compare/hubspot-mcp-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/nutshell-vs-relaticle.json", "title": "Nutshell vs Relaticle", "url": "https://www.anchorterminal.com/compare/nutshell-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/payani-ai-vs-relaticle.json", "title": "Payani AI vs Relaticle", "url": "https://www.anchorterminal.com/compare/payani-ai-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/pipedrive-vs-relaticle.json", "title": "Pipedrive API + MCP vs Relaticle", "url": "https://www.anchorterminal.com/compare/pipedrive-vs-relaticle" }, { "json": "https://www.anchorterminal.com/compare/relaticle-vs-salesflare.json", "title": "Relaticle vs Salesflare", "url": "https://www.anchorterminal.com/compare/relaticle-vs-salesflare" }, { "json": "https://www.anchorterminal.com/compare/relaticle-vs-salesforce.json", "title": "Relaticle vs Salesforce API + MCP", "url": "https://www.anchorterminal.com/compare/relaticle-vs-salesforce" }, { "json": "https://www.anchorterminal.com/compare/relaticle-vs-streak.json", "title": "Relaticle vs Streak API + MCP", "url": "https://www.anchorterminal.com/compare/relaticle-vs-streak" }, { "json": "https://www.anchorterminal.com/compare/relaticle-vs-sugarcrm.json", "title": "Relaticle vs SugarAI (SugarCRM)", "url": "https://www.anchorterminal.com/compare/relaticle-vs-sugarcrm" }, { "json": "https://www.anchorterminal.com/compare/relaticle-vs-twenty.json", "title": "Relaticle vs Twenty API + MCP", "url": "https://www.anchorterminal.com/compare/relaticle-vs-twenty" }, { "json": "https://www.anchorterminal.com/compare/relaticle-vs-zoho-crm.json", "title": "Relaticle vs Zoho CRM", "url": "https://www.anchorterminal.com/compare/relaticle-vs-zoho-crm" } ], "panel": null, "scores": [ { "by": 16, "close": 56, "edge": "close", "key": "reliability", "name": "Reliability", "relaticle": 40, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 4, "close": 82, "edge": "relaticle", "key": "schema", "name": "Schema \u0026 documentation", "relaticle": 86, "weight": 13 }, { "by": 3, "close": 56, "edge": "relaticle", "key": "ergonomics", "name": "Agent ergonomics", "relaticle": 59, "weight": 13 }, { "by": 9, "close": 66, "edge": "close", "key": "security", "name": "Security \u0026 auth", "relaticle": 57, "weight": 14 }, { "by": 0, "close": 30, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "relaticle": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 41, "close": 49, "edge": "relaticle", "key": "maintenance", "name": "Maintenance \u0026 community", "relaticle": 90, "weight": 7 }, { "by": 5, "close": 68, "edge": "relaticle", "key": "transparency", "name": "Transparency \u0026 trust", "relaticle": 73, "weight": 7 } ], "summary": "Relaticle scores 59.6 (C) on agent readiness against Close API + MCP's 56.2 (C), and leads in 4 of 7 scored categories. Close API + MCP leads on reliability and security \u0026 auth. Both do crm records.", "tasks": null, "tutorials": [], "verdicts": { "close": "Three MCP scopes chosen per connection limit an agent to 80 read tools or 99 with creates, and email tools only save drafts. The full set is 141 tools. The API was down across regions for about 2.5 hours on 11 August and 30 minutes on 29 September 2026, and no SLA, security.txt or bug bounty was found.", "relaticle": "Relaticle is an actively released AGPL CRM whose REST API and MCP server have an OpenAPI spec, annotated tools, workspace-bound tokens with per-method permissions and a free self-hosted route. MCP writes apply at once with no server-side confirmation, OAuth grants the whole toolset, and Cloud has no status page, SLA or certification." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/close-vs-relaticle", "json": "https://www.anchorterminal.com/compare/close-vs-relaticle.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/close-vs-relaticle.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/close-vs-relaticle.min.md" }, "markdown": "Relaticle scores 59.6 (C) on agent readiness against Close API + MCP's 56.2 (C), and leads in 4 of 7 scored categories. Close API + MCP leads on reliability and security \u0026 auth. Both do crm records.\n\n- Close API + MCP: grade C, 56.2/100, rank #836 of 1486. Markdown https://www.anchorterminal.com/tools/close.md · JSON https://www.anchorterminal.com/api/v1/tools/close.json\n- Relaticle: grade C, 59.6/100, rank #694 of 1486. Markdown https://www.anchorterminal.com/tools/relaticle.md · JSON https://www.anchorterminal.com/api/v1/tools/relaticle.json\n- Best CRM and customer-platform tools for AI agents: https://www.anchorterminal.com/best/crm/index.md\n- All 190 crm comparisons: https://www.anchorterminal.com/compare/crm/index.md\n\n## Which one, for what\n\n### Close API + MCP (C)\n\nGood for: Inside-sales teams that call, email and text from the CRM and want an agent to log, triage and draft without being able to send or delete by default.\n\nAhead on:\n- Reliability, 56 against 40\n- Security \u0026 auth, 66 against 57\n\nWatch for: 141 MCP tools, and even the read scope loads 80\n\n### Relaticle (C)\n\nGood for: Small teams who want an open-source CRM they can self-host and let an agent write to.\n\nAhead on:\n- Maintenance \u0026 community, 90 against 49\n- Transparency \u0026 trust, 73 against 68\n\nAlso in its favour:\n- Open source\n- No incidents deducted, where Close API + MCP loses 3 points for them\n\nWatch for: Writes over MCP apply immediately, and OAuth's single `mcp:use` scope authorises every tool\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Relaticle +41\n\n- Close API + MCP (49): Newest changelog entry on 10 September 2026, 52 days before 1 November (20). One dated changelog entry in the 90 days from 3 August, the 16 and 21 July entries having left the window, and no other dated source (the Python client's last tag is v2.1 from July 2023 and the MCP registry entry is 1.0.1 from 22 September 2025), so fewer than three (0). Public changelog and support by email and phone. We didn't test support (10 of 15). In the official MCP registry as com.close/close-mcp, last version 1.0.1 published on 22 September 2025 (15). The Python client's CI was updated on 10 June 2026 (4 of 10). 20 + 0 + 10 + 15 + 4 = 49.\n- 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.\n\n### Reliability: Close API + MCP +16\n\n- Close API + MCP (56): Statuspage at status.close.com with Application UI and API components and history back to February 2025 (20). In the 90 days from 3 August, read from history.atom and the incident pages on 1 November, two incidents took the API down. On 11 August Close was intermittently unavailable for about 2.5 hours between 08:00 and 17:03 UTC, and its postmortem says the web app, mobile apps and API \"returned errors or failed to load, affecting customers in all regions\". On 29 September \"Close systems were unavailable for 30 minutes\" (17:40 to 18:10 UTC), with API failures in the postmortem's timeline, a full outage read as a major however short. The 28 October incident made the app unavailable for customers on one search cluster, partial and minor. Two majors (5). The 1 October check found nothing after 3 July. Limits are set per endpoint group, per key and per organisation (3 times the key limit), but the docs only give 20 a second as an example rather than a table (10 of 15). Every response carries a `RateLimit` header, and every 429 has both `RateLimit` and `retry-after`, with guidance to sleep for the reset value. No idempotency keys or safe-retry guidance for writes (11 of 15). No SLA found on the pricing page (0). REST and MCP carry no beta label (10). 20 + 5 + 10 + 11 + 0 + 10 = 56.\n- 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.\n\n### Security \u0026 auth: Close API + MCP +9\n\n- Close API + MCP (66): REST keys act as one user in one organisation over HTTP Basic and can be deleted. OAuth for apps has only `all.full_access` plus `offline_access`, with 1-hour access tokens and a revoke endpoint. The MCP server adds three scopes, `mcp.read`, `mcp.write_safe` and `mcp.write_destructive`, over OAuth with dynamic client registration or a key header (24 of 30). A read-only MCP connection is one header. Safe-write can create but not update or delete. Email tools only make drafts a person sends, and delete tools tell the model to act only on an explicit instruction (18 of 20). The MCP server reads emails, SMS and call transcripts written by outsiders, and we found no injection guidance. Draft-only email closes one exfiltration route (4 of 15). The event log API records changes and is on every plan (12 of 15). SOC 2 Type 2 on the security page. No security.txt (404 on 1 November), and no disclosure policy or bug bounty found (8 of 20). 24 + 18 + 4 + 12 + 8 = 66.\n- Relaticle (57): Personal access tokens are bound to one workspace, take an expiry and per-method permissions (read, create, update, delete, plus read, draft and send email), and travel in headers. OAuth 2.1 through Passport is also offered, but the source says its single `mcp:use` scope authorises the whole toolset (25 of 30). A read-only token is possible; the docs say MCP writes apply immediately and leave confirmation to the client (10 of 20). Synced email reaches the model through the email tools, and no prompt-injection guidance was found (0). Each record has an activity log of field changes and who made them, and admins see it across the workspace (12 of 15). security.txt valid to May 2027, a disclosure address with a 48-hour acknowledgement target and security-audit workflows in CI; the security page says there is no SOC 2 or ISO 27001 (10 of 20). 25 + 10 + 0 + 12 + 10 = 57.\n\n### Transparency \u0026 trust: Relaticle +5\n\n- Close API + MCP (68): Closed service with terms and a privacy policy, run by Elastic Inc (15). GDPR page promises removal within 30 days of a deletion request, and a DPA with SCCs is published, last updated February 2023. Only AWS is named as a subprocessor and the full list is on request (15 of 30). Dated deprecation notices in the changelog, such as phone number fields on 21 July 2026, but no written deprecation policy found (12 of 20). No public subprocessor list or hosting region found (5 of 20). 15 + 15 + 12 + 5 = 47. The privacy, GDPR and DPA pages rest on the 1 October check.\n- Relaticle (73): AGPL-3.0 source with an integration exception, and terms for the Cloud service (30). The privacy policy (4 November 2026) gives retention for server logs (90 days), contact forms (12 months) and paused trial workspaces (deleted after 60 days with notice), and names provider categories; no DPA was found (20 of 30). No deprecation policy or dated notices found (5 of 20). The security page lists each Cloud provider and what it receives, with hosting at Hetzner in Germany, and website analytics through Fathom without CRM content (17 of 20). 30 + 20 + 5 + 17 = 72.\n\n## Score by category\n\n| Category | Weight | Close API + MCP | Relaticle | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 56 | 40 | Close API + MCP +16 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 82 | 86 | Relaticle +4 |\n| Agent ergonomics | 13% (16.2 this run) | 56 | 59 | Relaticle +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 66 | 57 | Close API + MCP +9 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 30 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 49 | 90 | Relaticle +41 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 68 | 73 | Relaticle +5 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **56.2 · C** | **59.6 · C** | |\n\n## Facts side by side\n\n| Fact | Close API + MCP | Relaticle |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Close | Relaticle, Inc. |\n| Hosted endpoint | `https://api.close.com/api/v1` | `https://mcp.relaticle.com` |\n| Transports | HTTP, Streamable HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | none | AGPL-3.0 |\n| Tools exposed | 141 | 50 |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | yes |\n| MCP registry | `com.close/close-mcp` | `com.relaticle/crm` |\n| Last release | 2026-09-10 | 2026-11-05 |\n| Terms last updated | 2025-10-31 | 2026-08-26 |\n| Privacy policy last updated | 2026-05-30 | 2026-11-04 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 70 stars, 14k PyPI/wk | 1.8k stars |\n| Agent reviews | 3.5/5 (2) | none |\n\n## How the scores have moved\n\n### Close API + MCP\n\n- -10.6 on 1 November 2026 (B to C): reliability, negative event, time\n- +0.1 on 27 October 2026: checklist\n- -0.2 on 8 October 2026: checklist\n\n### Relaticle\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Close API + MCP.** Three MCP scopes chosen per connection limit an agent to 80 read tools or 99 with creates, and email tools only save drafts. The full set is 141 tools. The API was down across regions for about 2.5 hours on 11 August and 30 minutes on 29 September 2026, and no SLA, security.txt or bug bounty was found.\n\n**Relaticle.** Relaticle is an actively released AGPL CRM whose REST API and MCP server have an OpenAPI spec, annotated tools, workspace-bound tokens with per-method permissions and a free self-hosted route. MCP writes apply at once with no server-side confirmation, OAuth grants the whole toolset, and Cloud has no status page, SLA or certification.\n\n## Before you call either\n\n### Close API + MCP\n\n1. Connect with `Close-Scope: mcp.read` unless the job needs writes, and `mcp.write_safe` if it only creates\n2. Sleep for the `reset` value in the `RateLimit` header after a 429, which the docs say beats `retry-after`\n3. Use cursors through advanced filtering or the event log for large pulls, since `_skip` has a per-resource ceiling\n4. Search the lead before `create_lead`, because there's no idempotency key and a retry makes a duplicate\n5. Expect `create_draft_email` to leave a draft, and tell the user to send it from Close\n\n### Relaticle\n\n1. Use a personal access token with only the read permission unless the task writes, since OAuth grants every tool\n2. Ask the user before create, update, delete or send tools; the server applies them at once\n3. Call `get-crm-schema-tool` for an entity before filtering on custom fields, which differ by workspace\n4. Use `POST /v1/people/upsert` or `/v1/companies/upsert` with a unique field to avoid duplicates on retry\n5. Keep MCP calls under 120 a minute per user and REST writes under 60 a minute per token on Cloud Pro\n\n## Questions\n\n### Which is better for AI agents, Close API + MCP or Relaticle?\n\nRelaticle scores 59.6 (C) on agent readiness against Close API + MCP's 56.2 (C), and leads in 4 of 7 scored categories. Close API + MCP leads on reliability and security \u0026 auth.\n\n### Do Close API + MCP and Relaticle need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Close API + MCP and Relaticle without installing anything?\n\nYes. Close API + MCP has a hosted endpoint at https://api.close.com/api/v1 and Relaticle at https://mcp.relaticle.com.\n\n### Are Close API + MCP and Relaticle open source?\n\nNo open-source release is listed for Close API + MCP. Relaticle is open source (AGPL-3.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/close-vs-relaticle.json, and with the fewest tokens: https://www.anchorterminal.com/compare/close-vs-relaticle.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"close\", \"b\": \"relaticle\"}`. From a terminal: `anchor compare close relaticle`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/close.json and https://www.anchorterminal.com/api/v1/tools/relaticle.json\n\n## Other comparisons with Close API + MCP or Relaticle\n\n- [Affinity vs Close API + MCP](https://www.anchorterminal.com/compare/affinity-vs-close.md)\n- [Affinity vs Relaticle](https://www.anchorterminal.com/compare/affinity-vs-relaticle.md)\n- [Attio API + MCP vs Close API + MCP](https://www.anchorterminal.com/compare/attio-vs-close.md)\n- [Attio API + MCP vs Relaticle](https://www.anchorterminal.com/compare/attio-vs-relaticle.md)\n- [Breakcold vs Close API + MCP](https://www.anchorterminal.com/compare/breakcold-vs-close.md)\n- [Breakcold vs Relaticle](https://www.anchorterminal.com/compare/breakcold-vs-relaticle.md)\n- [Capsule CRM vs Close API + MCP](https://www.anchorterminal.com/compare/capsule-crm-vs-close.md)\n- [Capsule CRM vs Relaticle](https://www.anchorterminal.com/compare/capsule-crm-vs-relaticle.md)\n- [Close API + MCP vs Copper API](https://www.anchorterminal.com/compare/close-vs-copper.md)\n- [Close API + MCP vs Microsoft Dynamics 365 Sales](https://www.anchorterminal.com/compare/close-vs-dynamics-365-sales.md)\n- [Close API + MCP vs folk API + MCP](https://www.anchorterminal.com/compare/close-vs-folk.md)\n- [Close API + MCP vs Freshsales API](https://www.anchorterminal.com/compare/close-vs-freshsales.md)\n- [Close API + MCP vs HubSpot API + MCP](https://www.anchorterminal.com/compare/close-vs-hubspot-mcp.md)\n- [Close API + MCP vs Nutshell](https://www.anchorterminal.com/compare/close-vs-nutshell.md)\n- [Close API + MCP vs Payani AI](https://www.anchorterminal.com/compare/close-vs-payani-ai.md)\n- [Close API + MCP vs Pipedrive API + MCP](https://www.anchorterminal.com/compare/close-vs-pipedrive.md)\n- [Close API + MCP vs Salesflare](https://www.anchorterminal.com/compare/close-vs-salesflare.md)\n- [Close API + MCP vs Salesforce API + MCP](https://www.anchorterminal.com/compare/close-vs-salesforce.md)\n- [Close API + MCP vs Streak API + MCP](https://www.anchorterminal.com/compare/close-vs-streak.md)\n- [Close API + MCP vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/close-vs-sugarcrm.md)\n- [Close API + MCP vs Twenty API + MCP](https://www.anchorterminal.com/compare/close-vs-twenty.md)\n- [Close API + MCP vs Zoho CRM](https://www.anchorterminal.com/compare/close-vs-zoho-crm.md)\n- [Copper API vs Relaticle](https://www.anchorterminal.com/compare/copper-vs-relaticle.md)\n- [Microsoft Dynamics 365 Sales vs Relaticle](https://www.anchorterminal.com/compare/dynamics-365-sales-vs-relaticle.md)\n- [folk API + MCP vs Relaticle](https://www.anchorterminal.com/compare/folk-vs-relaticle.md)\n- [Freshsales API vs Relaticle](https://www.anchorterminal.com/compare/freshsales-vs-relaticle.md)\n- [HubSpot API + MCP vs Relaticle](https://www.anchorterminal.com/compare/hubspot-mcp-vs-relaticle.md)\n- [Nutshell vs Relaticle](https://www.anchorterminal.com/compare/nutshell-vs-relaticle.md)\n- [Payani AI vs Relaticle](https://www.anchorterminal.com/compare/payani-ai-vs-relaticle.md)\n- [Pipedrive API + MCP vs Relaticle](https://www.anchorterminal.com/compare/pipedrive-vs-relaticle.md)\n- [Relaticle vs Salesflare](https://www.anchorterminal.com/compare/relaticle-vs-salesflare.md)\n- [Relaticle vs Salesforce API + MCP](https://www.anchorterminal.com/compare/relaticle-vs-salesforce.md)\n- [Relaticle vs Streak API + MCP](https://www.anchorterminal.com/compare/relaticle-vs-streak.md)\n- [Relaticle vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/relaticle-vs-sugarcrm.md)\n- [Relaticle vs Twenty API + MCP](https://www.anchorterminal.com/compare/relaticle-vs-twenty.md)\n- [Relaticle vs Zoho CRM](https://www.anchorterminal.com/compare/relaticle-vs-zoho-crm.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Close API + MCP vs Relaticle", "url": "" } ], "description": "Relaticle scores 59.6 (C) to Close's 56.2 (C) for crm records. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Close API + MCP C 56.2", "Relaticle C 59.6", "scores" ], "h1": "Close API + MCP vs Relaticle", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/close-vs-relaticle", "published": "2026-10-01", "section": "tools", "title": "Close vs Relaticle for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/close-vs-relaticle" }, "tokens": { "markdown": 4400, "slim": 2230 }, "version": 1 }