Nutshell vs Streak API + MCP

Nutshell

The REST reference is served as Markdown with an OpenAPI fragment per operation, and the hosted MCP server uses OAuth with PKCE and can only read. No rate limit numbers, error format or API changelog were found in the reviewed documentation, and API keys carry no scopes.

Streak API + MCP

MCP server is OAuth only and revocable from account settings. MCP tool list and count not published.

Nutshell

1. Authenticate REST calls with HTTP Basic, a Nutshell user's email as username and the API key as password, against https://app.nutshell.com/rest
2. Use IDs in the <number>-<type> form, such as 3-accounts, and send updates as JSON Patch with content-type: application/json-patch+json
3. Page lists with page[limit] and page[page], which is 0-based, and call /accounts/list/fields or the lead and contact equivalents for valid filter keys
4. Use the REST API for writes. The MCP server only reads, and OAuth tokens need the read scope
5. Filter webhook events yourself, because every webhook receives all events and subscriptions are created in Setup, not through the API

Streak API + MCP

1. Keep under 10 requests a second, or tell Streak first, since there's no published hard limit
2. Expect no email bodies through MCP and fetch thread context through Gmail instead
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