# Nutshell vs Relaticle (slim)

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

- Full: https://www.anchorterminal.com/compare/nutshell-vs-relaticle.md (~4,400 tokens) · this version ~2,230 tokens · JSON https://www.anchorterminal.com/compare/nutshell-vs-relaticle.json · canonical https://www.anchorterminal.com/compare/nutshell-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)

Relaticle scores 59.6 (C) on agent readiness against Nutshell's 49.4 (D), and leads in 4 of 7 scored categories. Nutshell leads on reliability and payments & pricing. Both do crm records.

- Nutshell: D 49.4, rank #1086 of 1486 · https://www.anchorterminal.com/tools/nutshell.min.md
- Relaticle: C 59.6, rank #694 of 1486 · https://www.anchorterminal.com/tools/relaticle.min.md
- Nutshell, good for Small sales teams already on Nutshell who want an agent to read and update pipeline data over MCP or REST at a low seat price. Ahead on Reliability, 45 against 40; Payments & pricing, 35 against 30.
- Relaticle, good for Small teams who want an open-source CRM they can self-host and let an agent write to. Ahead on Schema & documentation, 86 against 57; Agent ergonomics, 59 against 44; Maintenance & community, 90 against 36. Also Open source.

| Category | Nutshell | Relaticle |
| --- | --- | --- |
| Reliability (16%) | 45 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 57 | 86 |
| Agent ergonomics (13%) | 44 | 59 |
| Security & auth (14%) | 58 | 57 |
| Payments & pricing (10%) | 35 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 36 | 90 |
| Transparency & trust (7%) | 72 | 73 |

| Fact (where they differ) | Nutshell | Relaticle |
| --- | --- | --- |
| Vendor | Nutshell, Inc. | Relaticle, Inc. |
| Hosted endpoint | `https://app.nutshell.com/rest` | `https://mcp.relaticle.com` |
| Transports | HTTP | Streamable HTTP |
| Pricing | Paid | Freemium |
| Licence | Proprietary service under Nutshell's Terms of Service | AGPL-3.0 |
| Tools exposed | none | 50 |
| MCP registry | not listed | `com.relaticle/crm` |
| Last release | 2026-10-27 | 2026-11-05 |
| Terms last updated | 2026-06-02 | 2026-08-26 |
| Privacy policy last updated | 2026-06-02 | 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 | none | 1.8k stars |

Why the edge:
- Maintenance & community, Relaticle +54: Nutshell 36 (The MCP server help article, updated 27 October 2026, documents create and update tools that the 8 October reading did not find, a dated change to a listed surface 8 days before the check (30 of 30). The REST reference pages carry update stamps, the newest 21 August 2026, but the stamps record no API change, and the product updates page is undated, so no other dated entry counts. One dated change in the 90 days from 6 August (0). No API changelog. Live support on every plan per the pricing page, untested (6 of 25). No current official SDK, and the MCP registry was not checked (0). No packages to judge (0). 30 + 0 + 6 + 0 + 0 = 36.); 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.)
- Schema & documentation, Relaticle +29: Nutshell 57 (Each of the 114 REST reference pages carries the OpenAPI 3.0 definition of its operation, but whole-spec download is disabled (18 of 25). `llms.txt` and Markdown for every docs page (10). 78 of 114 operations have a description, and the newer ones state scope and visibility rules (11 of 20). Enums on sort fields and patterns on IDs, but filters and custom fields are open objects and `page[limit]` is typed as a string on some operations (9 of 15). Schema examples are present, and error responses appear on 9 operations with no error body schema (5 of 15). The spec is version 2.0.0 and pages carry update stamps, with no dated API changelog (4 of 15).); Relaticle 86 (OpenAPI 3.1 at /openapi.json and /openapi.yaml with 34 operations (25). llms.txt with a when-to-use and when-not section, and developer pages (10). The llms.txt and MCP docs say what the API is for and what it doesn't do (no email over REST, no meetings), while only 5 of 34 operations carry a description (14 of 20). 114 required lists and typed MCP inputs, but few enums (11 of 15). 661 examples and responses for 401, 402, 403, 404, 409, 422 and 429 (14 of 15). /v1 and frequent tagged releases, with no changelog page (relaticle.com/changelog is 404) (12 of 15). 25 + 10 + 14 + 11 + 14 + 12 = 86.)
- Agent ergonomics, Relaticle +15: Nutshell 44 (The MCP server has about 18 groups of search and report tools and six groups of create and update tools per the help centre, updated 27 October 2026. The tool definitions sit behind OAuth and were not read. REST lists take `page[limit]` with no field selection (13 of 25). `page[page]`, `sort`, `q` and `filter[...]` keys, with field lists from `/accounts/list/fields`, and no stated maximum page size (16 of 20). Error responses appear on 9 of 114 operations with no error body schema, partly met (4 of 20). No idempotency keys. Deletes can be undone within 30 days, and the MCP server cannot delete records, partly met (6 of 20). Few required fields, and no official REST SDK. The only client is a PHP JSON-RPC sample last pushed in 2023 (5 of 15).); Relaticle 59 (50 MCP tools, six schema resources and a prompt, with no toolsets or read-only subset (5). Filters combine native fields, custom fields and linked records with $and, $or and $not, plus sort, include, `per_page` (MCP maximum 25) and cursors (20). Errors come back as HTTP codes and inline MCP error responses such as `Invalid ability provided.`; no error catalogue was read (12 of 20). Base tool classes set readOnlyHint, destructiveHint, idempotentHint and openWorldHint, and upserts by unique field make creates safe to retry (17 of 20). One URL with OAuth or a token; no official SDK (5 of 15). 5 + 20 + 12 + 17 + 5 = 59.)
- Reliability, Nutshell +5: Nutshell 45 (Read with the hosted lines. Status page at status.nutshell.com with 12 components and history back to 2017. None is named for the REST API or the MCP server, and the Nutshell application component is the CRM app as a whole, read as a vendor page with no component for the product (15). The incident line is re-read from the page's history feed. In the 90 days from 6 August one incident touched the product, a database cluster fault on 28 September 2026 that left Nutshell unavailable for some customers, partial, so minor (20 of 30). The 21 October PHP2Shell response disabled landing pages, email link tracking and scheduler pages on custom domains, not the API, and the 12 August and 16 October entries are announced maintenance. No rate limit numbers for REST, and the JSON-RPC docs say only that limits vary (0). No 429, Retry-After, backoff or idempotency guidance found (0). No SLA found, and the terms supply the service as is (0). The REST API is GA and the MCP server carries no beta label (10). 15 + 20 + 0 + 0 + 0 + 10 = 45.); 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.)
- Payments & pricing, Nutshell +5: Nutshell 35 (No x402, MPP or L402 (0). Plan prices are public, $13 to $79 a seat a month billed yearly, with nothing per call (10). 14-day trial with no card, and the API is included (20). A person signs up in a browser and an admin creates the key. The docs publish sandbox credentials for a shared demo account, which lets an agent test calls with no signup but not reach its own data (5 of 20).); Relaticle 30 (No x402, MPP or L402 (0). Cloud prices are public per workspace with nothing per call (10). A 14-day Cloud Pro trial with no card, and self-hosting is free (20). A person signs up in a browser behind a Cloudflare check, or deploys a server (0). 0 + 10 + 20 + 0 = 30.)