Scratchattach MCP Server

MCP Server for Scratch, powered by scratchattach.

Local serverstdioPython

What is the Scratchattach MCP server?

Scratchattach MCP server exists for a simple reason — assistants are far more useful when they can act on Scratchattach directly instead of describing what you should do. MCP Server for Scratch, powered by scratchattach.

What you get

The agent can access the Scratch platform to interact with site features (e.g. social features), or code Scratch projects live.

What the assistant can call

Once Scratchattach is connected, these are the calls the assistant has available:

  • Sessions — The Sessions tool exposed by this server
  • Profile — The Profile tool exposed by this server
  • Comments — All four accept source of project, studio or profile
  • Reference — The Reference tool exposed by this server

Configuration and credentials

You will need one environment variable: PYTHONPATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Scratchattach's toolset — Sessions, Profile, Comments and 1 more — is a fair guide to whether it matches your workflow. It is maintained by uukelele-scratch; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the scratchattach mcp server does with a few real requests.

Available tools

ToolWhat it does
SessionsThe Sessions tool exposed by this server.
ProfileThe Profile tool exposed by this server.
CommentsAll four accept source of project, studio or profile.
ReferenceThe Reference tool exposed by this server.

How to install the Scratchattach MCP server

{
  "mcpServers": {
    "scratch": {
      "command": "/home/x/scratch-mcp/.venv/bin/python",
      "args": ["-m", "scratch_mcp"],
      "cwd": "/home/x/scratch-mcp",
      "env": { "PYTHONPATH": "/home/x/scratch-mcp" },
      "timeout": 600000 // compiling / decompiling / publishing can take quite some time
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
PYTHONPATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use Scratchattach to Sessions.
  • Use Scratchattach to Profile.
  • Use Scratchattach to Comments.

Frequently asked questions

It connects Scratchattach to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (Sessions, Profile, Comments, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Scratchattach directly.