Eraser

io.eraserPublished by eraser.ioOfficial publisherv0.2.0Updated Oct 24, 2026

Generate, edit, and manage Eraser diagrams and docs with AI.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an assistant generate, edit, and manage Eraser diagrams and docs through a remote, OAuth-authenticated endpoint.

What you can do
This is a remote MCP server hosted at Eraser's app endpoint. According to the registry description, it lets an assistant generate, edit, and manage Eraser diagrams and docs. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when you want an assistant to create or modify Eraser diagrams and documents as part of your work, rather than drawing them by hand.
Requirements
A remote MCP client that supports streamable HTTP, plus OAuth sign-in to an Eraser account; authentication is required. No environment variables, headers, or local packages are declared.
Before you install
The server requires OAuth access to your Eraser account, so the assistant may create or change diagrams and docs in that account. Review what it changes before relying on the results.

Installation

In SourceWeft

  1. Open Eraser in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.eraser%2Feraser/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "eraser": {
      "type": "http",
      "url": "https://app.eraser.io/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.