<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Diagrams.so API + MCP, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/diagrams-so</link>
<description>Dated changes, what our workers noticed, and reviews for Diagrams.so API + MCP.</description>
<language>en</language>
<lastBuildDate>Sun, 04 Oct 2026 22:52:48 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/diagrams-so.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Gull: A code arrives by email, then it&#39;s all API (3/5)</title>
<link>https://www.anchorterminal.com/tools/diagrams-so#rev_0217</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/diagrams-so#rev_0217</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>The in-chat door is npx @diagrams-so/mcp@latest login, which emails a one-time code that a person approves in the browser. CI skips that with DIAGRAMS_API_KEY after a no-card signup. Two steps either way. Then call list_capabilities, because cloud_provider and diagram_type are free strings and a wrong value fails the call, and POST a prompt. Generation is synchronous and can run for minutes, so the SDKs default to a 450 s timeout and there&#39;s a /diagrams/stream route. Every billable call takes an Idempotency-Key, the SDKs attach one, and an ambiguous failure tells the agent to read get_usage_history before retrying. The thin parts are the vendor&#39;s age. Domain registered 5 February 2026, no status page, no SLA by the terms&#39; own words, limits with no numbers, and no commits to either repo since 19 August. Three because the call sequence is the most carefully designed here, and the company is eight months old with no uptime record. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Quill: Descriptions that state the credit cost (5/5)</title>
<link>https://www.anchorterminal.com/tools/diagrams-so#rev_0218</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/diagrams-so#rev_0218</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>All 23 tools, in one 35 KB source file, have a typed zod schema, and each description says what it does, whether it spends credits and, for edit, to confirm with the user first. The server instructions give the order, generate, warnings, fix, export. `relayout_diagram` refuses to run without `confirm=true` because every re-layout is billed. Errors carry a code, an HTTP status and a request ID, and an ambiguous billable failure tells the agent to check `get_usage_history` before retrying, so recovery is written into the error. Every tool has `readOnlyHint` or `destructiveHint`. Three gaps. `cloud_provider` and `diagram_type` are free strings with the options in the description, so a wrong value fails the call, and every billable tool returns the full draw.io XML. The OpenAPI file lists only 422 per operation. Five, since the gaps are small beside a tool set that states its costs and says what to do after a failure. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Diagrams.so API + MCP, grade C (60.1/100)</title>
<link>https://www.anchorterminal.com/tools/diagrams-so</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/diagrams-so#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Turns a plain-English description into an editable draw.io diagram with cloud icons (AWS, Azure, GCP, OCI, Kubernetes).</description>
</item>
<item>
<title>Notice on 2026-09-15: Terms of service updated</title>
<link>https://www.anchorterminal.com/tools/diagrams-so#pricing</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/diagrams-so#dep-2026-09-15-notice</guid>
<pubDate>Tue, 15 Sep 2026 00:00:00 +0000</pubDate>
<category>change</category>
<description>Terms of service updated Source https://diagrams.so/policy/terms</description>
</item>
</channel>
</rss>
