Eraser for AI agents

Eraser is a workspace for creating and organizing technical diagrams and documents, used by engineering teams to document systems, architecture, and design decisions as they build. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect Eraser See the 42 actions ↓

DocumentsOAuth 2.0 (MCP)MCP + RESTeraser.io

AUDIT LOG · ERASERPOLICY: acme-support

09:41:07 · claude · u_8f2read

eraser.list_files

List files✓ allowed · 212ms

09:41:08 · claude · u_8f2read

eraser.get_me

Get me✓ allowed · 164ms

09:41:09 · claude · u_8f2write

eraser.create_file

Create file✓ approved · approved by user

09:41:12 · claude · u_8f2destructive

eraser.delete_file

Delete file✕ blocked · policy: deny

EVERY ERASER CALL, ON THE RECORD

01 · USE CASES

What agents do in Eraser.

Create a diagram from a description

Create a diagram of a system based on notes an engineer provides during a design discussion.

Pull an existing diagram

Get a saved diagram to update it with a new component before a review.

Confirm before deleting a document

Require approval before deleting a document, since teammates may still be referencing it.

02 · ACTIONS

42 Eraser actions, graded by risk.

Every Eraser action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

Look things up. Allowed by default.

eraser.get_me
Get me
eraser.get_file
Get file
eraser.get_folder
Get folder
eraser.get_preset
Get preset
eraser.list_files
List files
eraser.list_teams
List teams
eraser.get_diagram
Get diagram
eraser.get_document
Get document
eraser.list_folders
List folders
eraser.list_presets
List presets
eraser.list_diagrams
List diagrams
eraser.get_template_or_reference
Get template or reference
eraser.search
Search
eraser.export_file
Export file
eraser.export_diagram
Export diagram
eraser.export_document
Export document

write

Create and change things. Allow, or ask the user first.

eraser.create_file
Create file
eraser.update_file
Update file
eraser.update_rules
Update rules
eraser.create_folder
Create folder
eraser.create_preset
Create preset
eraser.update_folder
Update folder
eraser.update_preset
Update preset
eraser.create_diagram
Create diagram
eraser.update_diagram
Update diagram
eraser.create_document
Create document
eraser.update_document
Update document
eraser.create_template_or_reference
Create template or reference
eraser.update_template_or_reference
Update template or reference
eraser.select_team
Select team
eraser.manually_update_file
Manually update file
eraser.manually_create_diagram
Manually create diagram

+ 4 MORE

destructive

Delete, cancel or archive. Ask first, or deny outright.

eraser.delete_file
Delete file
eraser.delete_folder
Delete folder
eraser.delete_preset
Delete preset
eraser.delete_diagram
Delete diagram
eraser.delete_document
Delete document
eraser.add_or_remove_template_or_reference
Add or remove template or reference

03 · HOW IT WORKS

Eraser in three steps.

01Your users connect EraserThey sign in to Eraser on Arc0 Connect, under your brand, and approve the access you ask for.
02You set the rulesReads run, writes like “create file” can wait for the user, and “delete file” can be denied outright.
03Any agent can actYour agent calls Eraser through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.

POLICY.TS

await arc0.policies.set('eraser', {
  read: 'allow',
  write: 'ask',        // create_file
  destructive: 'deny',  // delete_file
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2

04 · AUTH AND DATA

How Eraser connects.

Eraser runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches Eraser through the same endpoint, policies and audit log as every other app.

The same Eraser connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH: OAuth 2.0 (MCP)
CREDENTIALS: Per-tenant encrypted vault
MODEL SEES: Results only, never credentials
AUDIT LOG: Every call, on every plan

05 · WORKS WITH

Use Eraser from any agent.

Claude

ChatGPT

Cursor

Codex

VS Code

OpenAI Agents SDK

Claude Agent SDK

Vercel AI SDK

Mastra

LangGraph

06 · RELATED

Eraser and Arc0, answered.

Q01

Can I use Eraser with Claude, ChatGPT or Cursor?

Yes. Connect Eraser to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Eraser actions you allow.

Q02

How do users connect Eraser?

Q03

Which Eraser actions can my agent take?

42 in total: 16 read, 20 write and 6 destructive, such as “create file”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Eraser?

Yes. Actions like “delete file” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Eraser too?

Yes. The same Eraser connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Eraser into your agent.

Your users connect Eraser once, under your brand. Your agent gets 42 actions behind your policies, with every call on the record.

Connect Eraser Browse all apps →

Free to build · MCP + REST · Audit log on every plan