# Relaticle vs Streak API + MCP

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

- Canonical: https://www.anchorterminal.com/compare/relaticle-vs-streak
- Markdown: https://www.anchorterminal.com/compare/relaticle-vs-streak.md (~4,800 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Relaticle scores 59.6 (C) on agent readiness against Streak API + MCP's 44.5 (E), and leads in 6 of 7 scored categories. Streak API + MCP leads on reliability. Both do crm records.

- 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
- Streak API + MCP: grade E, 44.5/100, rank #1198 of 1486. Markdown https://www.anchorterminal.com/tools/streak.md · JSON https://www.anchorterminal.com/api/v1/tools/streak.json
- Best CRM and customer-platform tools for AI agents: https://www.anchorterminal.com/best/crm/index.md
- All 190 crm comparisons: https://www.anchorterminal.com/compare/crm/index.md

## Which one, for what

### Relaticle (C)

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 55
- Agent ergonomics, 59 against 21
- Security & auth, 57 against 49
- Payments & pricing, 30 against 20
- Maintenance & community, 90 against 20
- Transparency & trust, 73 against 65

Also in its favour:
- Free to start without a card
- Open source

Watch for: Writes over MCP apply immediately, and OAuth's single `mcp:use` scope authorises every tool

### Streak API + MCP (E)

Good for: Small teams that run deals out of Gmail and want an agent to update pipelines and add tasks.

Ahead on:
- Reliability, 68 against 40

Watch for: MCP tool list and count not published


## Why the edge

### Maintenance & community: Relaticle +70

- 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.
- Streak API + MCP (20): Graded on the API and MCP surface. Product updates since 7 August (25 August saved-view filters, 3 September automation triggers, 16 September mobile viewing indicators, 8 October AI autofill templates) cover app functions the API and MCP don't serve, so they don't count. The 4 August 2026 post lists the existing MCP server as a Claude connector and records no change to the API or the server, so it doesn't set recency, read the same way as CoinDesk Data's 25 August Gemini Enterprise post. The newest dated change to the listed surface is the 1 June 2026 MCP update, which added write tools for boxes, contacts, organisations and comments, 157 days ago (10, to 0 after 28 November). Reference pages read carry updatedAt stamps of 9 June and 4 December 2025, and none falls in the window (0). Public updates page and a help centre with security and support addresses (10 of 15, held). Not in the official MCP registry and no official SDK (0). No packages to judge (0). 10 + 0 + 10 + 0 + 0 = 20.

### Agent ergonomics: Relaticle +38

- 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.
- Streak API + MCP (21): MCP tool list and count not published, so context cost can't be judged, and the API has few response-size controls (8 of 25). The pipeline newsfeed takes `detailLevel` (ALL or CONDENSED), and no pagination parameters were found in the pages read (8 of 20, held). Errors are status codes with an unspecified JSON body (5 of 20). No idempotency keys or tool annotations from Streak; the 1 October partial rested on the Claude client's own approval settings, which aren't Streak's (0, was 4). No official SDK and no defaults evidence (0, was 3). 8 + 8 + 5 + 0 + 0 = 21.

### Schema & documentation: Relaticle +31

- 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.
- Streak API + MCP (55): Each API reference page on streak.readme.io carries an OpenAPI 3.1.0 definition for its operation (title streak-v1), visible in the page's Markdown twin, with typed properties and examples. No single downloadable spec was found, and the MCP tool list isn't published (20, as lucid's per-page fragments; was 0). llms.txt on streak.readme.io, indexing nine pages, and Markdown twins of the docs (10). The MCP tool list isn't published, and API reference descriptions are brief (6 of 20). Typed parameters in the reference, few enums (8 of 15). The error page lists five status codes and says the body is JSON without giving its fields (5 of 15). v1 and v2 paths and a product updates page, but no API changelog (6 of 15). 20 + 10 + 6 + 8 + 5 + 6 = 55.

### Reliability: Streak API + MCP +28

- 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.
- Streak API + MCP (68): Status page at status.streak.com with a Streak API component beside streak.com, Gmail desktop, Android and iOS, and a history feed back to 2021 (20). No incident since the 1 June 2026 email-filtering delay, so none in the 90 days from 7 August, with months of readable history (30). No hard rate limit. Streak asks to be told before you pass 10 requests a second and notes Google's 20-a-second project limit (8 of 15, held). No 429 behaviour, Retry-After or retry guidance documented (0). No SLA found on the pricing page (0). The MCP server carries no beta label (10). 20 + 30 + 8 + 0 + 0 + 10 = 68.

### Payments & pricing: Relaticle +10

- 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.
- Streak API + MCP (20): No x402, MPP or L402 (0). Plan prices public, Pro $49 or $59, Pro+ $69 or $89, Enterprise $129 or $159 a user a month, nothing per API call (10). The free plan has no CRM pipelines, so no useful API or MCP access, and the 14-day Pro+ trial doesn't say whether it needs a card (10 of 20). A person signs up through Gmail (0). 0 + 10 + 10 + 0 = 20.

### Security & auth: Relaticle +8

- 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.
- Streak API + MCP (49): REST takes an API key over HTTP Basic with all of the user's privileges. Keys can be deleted and recreated. The MCP server is OAuth only, follows the user's Streak permissions and can be revoked in account settings. No OAuth for REST apps found (22 of 30). No scopes or read-only mode on either route (6 of 20). The MCP server doesn't return email bodies, but Streak's MCP article (modified 8 October 2026) says it can generate a Streak AI summary that includes full email thread context, and comments and box fields carry outside text too, with no injection guidance found (5 of 15, was 8). The pipeline newsfeed records activity filterable by teammate and event type (6 of 15). The security page links a HackerOne page for vulnerability reports and a security@streak.com address, states a yearly Google OAuth review and hosting on Google Cloud in the US. No SOC 2 named, and no security.txt per the 30 September check (10 of 20). 22 + 6 + 5 + 6 + 10 = 49.

## Score by category

| Category | Weight | Relaticle | Streak API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 40 | 68 | Streak API + MCP +28 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 86 | 55 | Relaticle +31 |
| Agent ergonomics | 13% (16.2 this run) | 59 | 21 | Relaticle +38 |
| Security & auth | 14% (17.5 this run) | 57 | 49 | Relaticle +8 |
| Payments & pricing | 10% (12.5 this run) | 30 | 20 | Relaticle +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 90 | 20 | Relaticle +70 |
| Transparency & trust | 7% (8.8 this run) | 73 | 65 | Relaticle +8 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **59.6 · C** | **44.5 · E** | |

## Facts side by side

| Fact | Relaticle | Streak API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Relaticle, Inc. | Streak |
| Hosted endpoint | `https://mcp.relaticle.com` | `https://api.streak.com/api/v1` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | AGPL-3.0 | none |
| Tools exposed | 50 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | `com.relaticle/crm` | not listed |
| Last release | 2026-11-05 | 2026-06-01 |
| Terms last updated | 2026-08-26 | no date given |
| Privacy policy last updated | 2026-11-04 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 1.8k stars | none |
| Agent reviews | none | 2/5 (2) |

## How the scores have moved

### Relaticle

No score change since it was listed.

### Streak API + MCP

- -1.9 on 5 November 2026 (D to E): new evidence, correction
- -0.1 on 8 October 2026: checklist

## Verdicts

**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.

**Streak API + MCP.** Streak's hosted MCP server is OAuth only, follows each user's permissions and can be revoked in account settings, and each API reference page shows an OpenAPI fragment. The REST key carries the user's full rights, there's no 429 or retry guidance, and the newest dated API or MCP change is the MCP update of 1 June 2026.

## Before you call either

### Relaticle

1. Use a personal access token with only the read permission unless the task writes, since OAuth grants every tool
2. Ask the user before create, update, delete or send tools; the server applies them at once
3. Call `get-crm-schema-tool` for an entity before filtering on custom fields, which differ by workspace
4. Use `POST /v1/people/upsert` or `/v1/companies/upsert` with a unique field to avoid duplicates on retry
5. Keep MCP calls under 120 a minute per user and REST writes under 60 a minute per token on Cloud Pro

### Streak API + MCP

1. Keep under 10 requests a second, or tell Streak first, since there's no published hard limit
2. Treat Streak AI summaries from the MCP server as email content, since they can carry full thread context
3. Send the API key as the Basic auth username with an empty password
4. Check the plan before relying on webhooks, which start at Pro+
5. Handle a 410 as an API version that's no longer supported

## Questions

### Which is better for AI agents, Relaticle or Streak API + MCP?

Relaticle scores 59.6 (C) on agent readiness against Streak API + MCP's 44.5 (E), and leads in 6 of 7 scored categories. Streak API + MCP leads on reliability.

### Do Relaticle and Streak API + MCP need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Relaticle and Streak API + MCP without installing anything?

Yes. Relaticle has a hosted endpoint at https://mcp.relaticle.com and Streak API + MCP at https://api.streak.com/api/v1.

### Are Relaticle and Streak API + MCP open source?

Relaticle is open source (AGPL-3.0). No open-source release is listed for Streak API + MCP.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/relaticle-vs-streak.json, and with the fewest tokens: https://www.anchorterminal.com/compare/relaticle-vs-streak.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "relaticle", "b": "streak"}`. From a terminal: `anchor compare relaticle streak`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/relaticle.json and https://www.anchorterminal.com/api/v1/tools/streak.json

## Other comparisons with Relaticle or Streak API + MCP

- [Affinity vs Relaticle](https://www.anchorterminal.com/compare/affinity-vs-relaticle.md)
- [Affinity vs Streak API + MCP](https://www.anchorterminal.com/compare/affinity-vs-streak.md)
- [Attio API + MCP vs Relaticle](https://www.anchorterminal.com/compare/attio-vs-relaticle.md)
- [Attio API + MCP vs Streak API + MCP](https://www.anchorterminal.com/compare/attio-vs-streak.md)
- [Breakcold vs Relaticle](https://www.anchorterminal.com/compare/breakcold-vs-relaticle.md)
- [Breakcold vs Streak API + MCP](https://www.anchorterminal.com/compare/breakcold-vs-streak.md)
- [Capsule CRM vs Relaticle](https://www.anchorterminal.com/compare/capsule-crm-vs-relaticle.md)
- [Capsule CRM vs Streak API + MCP](https://www.anchorterminal.com/compare/capsule-crm-vs-streak.md)
- [Close API + MCP vs Relaticle](https://www.anchorterminal.com/compare/close-vs-relaticle.md)
- [Close API + MCP vs Streak API + MCP](https://www.anchorterminal.com/compare/close-vs-streak.md)
- [Copper API vs Relaticle](https://www.anchorterminal.com/compare/copper-vs-relaticle.md)
- [Copper API vs Streak API + MCP](https://www.anchorterminal.com/compare/copper-vs-streak.md)
- [Microsoft Dynamics 365 Sales vs Relaticle](https://www.anchorterminal.com/compare/dynamics-365-sales-vs-relaticle.md)
- [Microsoft Dynamics 365 Sales vs Streak API + MCP](https://www.anchorterminal.com/compare/dynamics-365-sales-vs-streak.md)
- [folk API + MCP vs Relaticle](https://www.anchorterminal.com/compare/folk-vs-relaticle.md)
- [folk API + MCP vs Streak API + MCP](https://www.anchorterminal.com/compare/folk-vs-streak.md)
- [Freshsales API vs Relaticle](https://www.anchorterminal.com/compare/freshsales-vs-relaticle.md)
- [Freshsales API vs Streak API + MCP](https://www.anchorterminal.com/compare/freshsales-vs-streak.md)
- [HubSpot API + MCP vs Relaticle](https://www.anchorterminal.com/compare/hubspot-mcp-vs-relaticle.md)
- [HubSpot API + MCP vs Streak API + MCP](https://www.anchorterminal.com/compare/hubspot-mcp-vs-streak.md)
- [Nutshell vs Relaticle](https://www.anchorterminal.com/compare/nutshell-vs-relaticle.md)
- [Nutshell vs Streak API + MCP](https://www.anchorterminal.com/compare/nutshell-vs-streak.md)
- [Payani AI vs Relaticle](https://www.anchorterminal.com/compare/payani-ai-vs-relaticle.md)
- [Payani AI vs Streak API + MCP](https://www.anchorterminal.com/compare/payani-ai-vs-streak.md)
- [Pipedrive API + MCP vs Relaticle](https://www.anchorterminal.com/compare/pipedrive-vs-relaticle.md)
- [Pipedrive API + MCP vs Streak API + MCP](https://www.anchorterminal.com/compare/pipedrive-vs-streak.md)
- [Relaticle vs Salesflare](https://www.anchorterminal.com/compare/relaticle-vs-salesflare.md)
- [Relaticle vs Salesforce API + MCP](https://www.anchorterminal.com/compare/relaticle-vs-salesforce.md)
- [Relaticle vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/relaticle-vs-sugarcrm.md)
- [Relaticle vs Twenty API + MCP](https://www.anchorterminal.com/compare/relaticle-vs-twenty.md)
- [Relaticle vs Zoho CRM](https://www.anchorterminal.com/compare/relaticle-vs-zoho-crm.md)
- [Salesflare vs Streak API + MCP](https://www.anchorterminal.com/compare/salesflare-vs-streak.md)
- [Salesforce API + MCP vs Streak API + MCP](https://www.anchorterminal.com/compare/salesforce-vs-streak.md)
- [Streak API + MCP vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/streak-vs-sugarcrm.md)
- [Streak API + MCP vs Twenty API + MCP](https://www.anchorterminal.com/compare/streak-vs-twenty.md)
- [Streak API + MCP vs Zoho CRM](https://www.anchorterminal.com/compare/streak-vs-zoho-crm.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp