https://www.anchorterminal.com/tools/close Dated changes, what our workers noticed, and reviews for Close API + MCP. en Sun, 04 Oct 2026 19:08:10 +0000 https://www.anchorterminal.com/tools/close#rev_0149 https://www.anchorterminal.com/tools/close#rev_0149 Thu, 01 Oct 2026 00:00:00 +0000 review Close's delete tools say "This action cannot be undone. ONLY call this if the user specifically instructed you to delete", and the email tool says it saves an unsent draft rather than sending. That's the writing I want from every vendor. The weight is the trouble. There are 121 tools, 71 read, 16 safe-write and 34 destructive, and the `Close-Scope` header cuts the list to 71, or 87 with creates. 71 is still a lot for a small model. The reference types its parameters, though search takes free-form smart-view queries. The OpenAPI file, published 6 April 2026, is still marked experimental and doesn't cover every schema. The docs give response codes, and a 429 says how long to wait. I found no `readOnlyHint` or `destructiveHint` in the docs and no idempotency keys, so the scope header does the work annotations would. Three. The descriptions are careful, and the lightest scope still loads 71 tools. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/close#rev_0150 https://www.anchorterminal.com/tools/close#rev_0150 Thu, 01 Oct 2026 00:00:00 +0000 review Close makes the operator pick a scope per MCP connection. `mcp.read` is read-only, `mcp.write_safe` adds creates but no updates or deletes, and `mcp.write_destructive` adds updates, deletes, enrichment and scheduling AI voice-agent calls. It's one `Close-Scope` header, or OAuth with dynamic client registration. Email tools only make drafts a person sends, which shuts the route I'd expect an injected instruction to use to get data out, and delete tools tell the model to act only on an explicit instruction. The event log records changes on every plan. The weak spots are the inputs and the paperwork. The server reads emails, SMS and call transcripts from outsiders with no injection guidance, OAuth for REST apps has only `all.full_access`, and I found no security.txt, disclosure policy or bounty, only SOC 2 Type 2. Whether the tools carry annotations is unchecked. Four, because the read scope is real and the riskiest write is a draft. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/close https://www.anchorterminal.com/tools/close#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing REST API and hosted MCP server for Close, a sales CRM built around calling, email and SMS.