# Edit with Codex or Claude Code

## Connect an assistant to the editor.

Rasterloom includes a local MCP server for Codex, Claude Code and other clients
that support MCP over stdio. Open Rasterloom → Settings → Connections to set up
Codex or Claude Code, view connection status, disconnect, or copy configuration
for another client.

A connected assistant can inspect artboards and layers, create and format text,
add shapes and paths, adjust placement and layer appearance, work with masks,
and export artwork through supported editor tools. Discover the connected
server's tool list and parameter schemas before making changes; available
operations depend on the installed app version. Start with `rasterloom_status`
and `rasterloom_capabilities` to discover the document state, supported values
and available catalogs. The bundled automation guide covers MCP workflows and
stable accessibility identifiers for computer use.

The server runs locally. The assistant's model and data handling depend on the
client you connect. Document information returned to a client may be sent to
that client's service under its own policies.

## Manual setup

For Rasterloom installed in `/Applications`, register the bundled helper with
Codex:

```sh
codex mcp add rasterloom -- /Applications/Rasterloom.app/Contents/Helpers/rasterloom-mcp
```

For Claude Code:

```sh
claude mcp add --scope user rasterloom -- /Applications/Rasterloom.app/Contents/Helpers/rasterloom-mcp
```

For another stdio client, use the absolute path to the helper as its server
command. The helper requires no arguments or environment variables. Rasterloom's
Help menu can copy the server path if the app is installed elsewhere.

## Working with a document

Layer and tab inspection return objects containing `layers` and `tabs` arrays.
An agent-created canvas starts without a placeholder layer. Text creation accepts
color and tracking together; font discovery includes families, styles and exact
PostScript names. Opened project copies keep a source-based tab name.

Inspection remains available while an edit waits for project I/O or rendering.
Requests have bounded timeouts and support cancellation. If a call times out,
inspect the document before retrying: an edit completed before cancellation is
not automatically undone.

Inspect the current document before editing. Use the user's requested files,
artboards and layers, and verify the result after each group of changes. Use
only operations advertised by the connected server. Some editor features are
available through the app interface without a corresponding MCP tool.

An editor request can launch Rasterloom. Connecting the server does not grant
an assistant permission to edit unrelated documents, replace files or publish
exports. The user's task determines which actions are authorized.

## Discover the available operations

Use `tools/list` to read the connected server’s tool names and input schemas.
Use `resources/list` to find its documentation; if an automation guide is
advertised, read it with `resources/read` before starting an editing workflow.
The installed server is the authority for which operations are available.

1. Inspect the open document and its artboards and layers. Use the IDs returned
   by the server rather than guessing names or positions.
2. Make the edits requested by the user with the available tools.
3. Inspect the result before exporting or moving to another group of changes.

Check the [privacy page](https://rasterloom.com/privacy/) before sharing document information with
a connected client. For connection problems, [contact support](https://rasterloom.com/support/).