AgentPhone
Give an AI agent its own US or Canada number to call and text.
Generate architecture diagrams, ERDs and technical docs from natural language and manage your Eraser workspace.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Eraser MCP server connects Eraser's diagrams-as-code workspace to Claude, ChatGPT and any MCP-compatible agent. It exposes 10 tools that generate architecture diagrams, ERDs, sequence diagrams and technical documents from natural language, then create, read, update, search, export and delete the files, diagrams, folders and AI presets holding them.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
No. Eraser's MCP documentation states the server is free to use and subject to the same free tier limits as in-app usage. Those limits bite quickly though. Eraser's pricing page lists the Free plan at 3 files and 3 AI credits, so an agent generating diagrams exhausts a free workspace in three calls before any plan gate is reached.
Diagrams and folders, not files. Eraser's documentation states files must be archived before they can be deleted, and archiving is a soft delete recoverable from the Archived page of the dashboard. Deleting a folder archives the files inside it rather than destroying them. Individual diagrams inside a file are the one thing the connector removes outright.
Usually yes, through version history rather than a trash can. Eraser writes a new file version after 30 minutes of inactivity following edits, and you can restore or duplicate any earlier version. Retention is plan-gated: Eraser's pricing page lists 7 days on Free, 90 days on Starter, and unlimited on Business and Enterprise.
Yes, for generation only. Eraser's MCP FAQ states that calls involving AI generation use AI credits from your account. Reading, listing, searching and exporting do not. Which balance is charged depends on how you signed in: OAuth requests draw the signed-in user's credits, and API key requests draw team-level credits instead.
No, it only chooses which team is active. Eraser documents that a user can belong to multiple teams and switch between them, so one OAuth grant reaches every team your account is a member of. The connector selects a team for subsequent operations rather than being confined to one, which makes your team memberships the real access boundary.
Not through the OAuth consent screen. Eraser's own protected-resource descriptor advertises a single wildcard scope, so there is no read-versus-write split to decline at authorisation. The connector inherits whatever your Eraser account can already do. If you need a narrower grant, connect from an account with narrower team membership.
It depends on how you authenticated. Eraser's MCP FAQ states that OAuth-created files are made under your identity and private by default, while API key files are created under the team and attributed to the team. You can change access level and link sharing afterwards in the Eraser app or through the update tool.
Yes, with an API key passed as a bearer token on the Authorization header. Eraser documents this path for pipelines, headless environments and clients without OAuth support such as Microsoft Copilot Studio. One catch is easy to miss: Eraser's agent integration docs state that API tokens require a paid subscription and cannot be created on the free plan.
https://docs.eraser.io/docs/mcp 301-redirects here; the final 200 is cited. · retrieved 2026-08-19eraserlabs/eraser-io — https://github.com/eraserlabs/eraser-io/tree/main/packages/eraser-mcp (fetched 2026-08-19) · retrieved 2026-08-19initialize probe returning 401 with WWW-Authenticate — 2026-08-19 · retrieved 2026-08-19docs.eraser.io/robots.txt and docs.eraser.io/llms.txt (fetched 2026-08-19). Robots allows all documentation paths; no Content-Signal directive is present. · retrieved 2026-08-19Connect Eraser once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.