Local board MCP server
Add Irakasi's board MCP server to your AI app and connect your boards to it.
The local board MCP server (the @irakasi/board-mcp package) is a small program that runs on your computer and gives your AI app the tools to view and edit boards. You set it up and connect tabs in the Local board MCP server section of the Use AI with this board dialog in the Board header:
- Set up once per AI app: add the server to each AI app you use (see Adding the server to your AI app).
- Connect each browser tab: a board must be open in a connected browser tab for your assistant to edit it. A connected tab stays connected when you open another board in it (see Connecting a board).
- Add files and generate or edit images: if your AI app supports image generation, your assistant can create or edit images directly on the board (see Creating and editing images). It can also add images, videos, and other files from your computer, whereas Board WebMCP needs a web link or a small file sent in the message.
What you need
Before setting up the local server, make sure you have:
- Node.js 20 or newer: installed on your computer so your AI app can run the server package.
- A compatible AI app: an AI app on your computer that can run local MCP servers.
- An open board tab: the board open in your browser so you can connect its tab to the server.
Adding the server to your AI app
You do this once for each AI app. If your AI app can change its own settings, the quickest way is to ask it. Copy this prompt into your AI app:
Add Irakasi's board MCP server to your MCP settings. It is the npm package @irakasi/board-mcp (https://www.npmjs.com/package/@irakasi/board-mcp). Run it with the command `npx -y @irakasi/board-mcp@latest stdio` and name it irakasi-boards. When you are done, tell me how to restart you so the server loads.
Setting it up yourself

You can also copy the setup for your AI app from the connection dialog:
- Operation:
- Open Use AI with this board in the Board header.
- In the Local board MCP server section, open Setup instructions and choose your AI app.
- Copy its setup and add it to your AI app as the instructions say.
- Quit and reopen your AI app.
- Result: your AI app can start the server when your assistant uses Irakasi.
Where each AI app keeps its MCP setup:
| AI app | Where the setup goes |
|---|---|
| Claude Code | A command you run once in your terminal. |
| Claude Desktop | Settings > Developer > Edit Config, in claude_desktop_config.json. |
| Codex | ~/.codex/config.toml. |
| Cursor | ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one project. |
| Gemini | A command you run once, or ~/.gemini/settings.json. |
| Custom | Any other app that can run local MCP servers, including apps for local models. |
Connecting a board

Connect an open board tab in your browser to the local server:
- Operation:
- Ask your assistant to use Irakasi, for example "List my Irakasi boards". Some AI apps start the server only when your assistant first uses it, so this makes sure it is running.
- Open Use AI with this board in the Board header.
- In the Local board MCP server section, choose Connect to local server.
- Needs: the server added to your AI app.
- Result: the tab connects to the server, and your assistant can work on the board open in it.
The Local board MCP server section shows one of these statuses:
- Not paired: this tab is not connected.
- Connecting: the tab is connecting to the server.
- Waiting for the local server: Irakasi waits up to a minute for your AI app to start the server. Stop connecting cancels the wait.
- Waiting for an AI app: the tab is connected to the server, but no AI app is connected to it right now.
- Connected: the tab is connected and at least one AI app is using the server. The section also shows the server version and how many AI apps are connected.
- Local server disconnected: the tab lost its connection to the server, for example after you quit your AI app. It reconnects automatically when the server starts again.
Once a tab is connected:
- Stays connected in this tab: the connection lasts while the tab stays open, including after you reload the page or open another board in the same tab.
- Multiple tabs and AI apps: you can connect several board tabs to the same server, and several AI apps can use it at once.
- Disconnect: choose Disconnect from local server to end the tab's connection to the local server (Board WebMCP keeps working).
To stop one agent's access while keeping the tab connected:
- Operation: open Agent activity below the connection button and turn on Block access on that agent's card.
- Result: the agent's name dims and the button turns red. Its queued and new requests are refused across Irakasi tabs in this browser, including after a page reload; a request already running finishes.
- Allow access again: turn the block off. Restarting the AI app starts a new, unblocked connection (see Blocking an agent).
Your other boards
Through any connected tab, your assistant can also read your other boards saved in this browser without opening them, by exact name or by Board ID:
- Edit another board's contents: to change a board's shapes or animations, your assistant opens that board in a connected tab.
- Manage saved boards: your assistant can rename, duplicate, or delete saved boards without opening them. Deleting a board this way cannot be undone.
Adding images and files to the board
With the local server, your assistant can generate or edit images with its own image tools and add files from your computer directly to the board:
- AI image generation and editing: if your AI app supports image generation, your assistant can create new images and place them on the board, or edit existing images on the board (including selected areas, layers, and masks in the Image Editor; see Creating and editing images). For an image Codex generates in your conversation, your assistant identifies that exact image before adding it.
- Private staging folder: by default, the server creates its own private folder on your computer and reads files only from there. Your assistant knows where that folder is and saves or copies a file into it before adding it to the board.
- Your own folders: to let your assistant add files straight from your own folders, such as
Pictures, add those folders to the server's setup (see the @irakasi/board-mcp package page). - Codex approval: when Codex asks to import a file, choose Allow for this session to approve further imports in that session. Editing images or managing boards may need separate approval.
Updates and restarts
The setup asks for the latest published version each time the server starts, so you never need to reinstall it:
- Load a newer version: your AI app usually starts the server when you open the app or begin a new conversation, and a running server keeps its version until it restarts. When the board needs a newer version, the Local board MCP server section shows a notice asking you to restart the server from your AI app, or quit and reopen the app.
- Reconnect after a pause: your AI app's connection can close when your assistant has not used Irakasi for 2 hours, even while a board is connected. If your assistant can no longer reach Irakasi, restart the MCP connection in your AI app, or quit and reopen the app.
Privacy
The local board MCP server keeps access scoped to your computer and the tabs you connect:
- Local-only connections: the server runs only on your computer and accepts connections only from programs running under your user account on the same computer.
- Connected tabs only: the server reaches only the board tabs you connect, and reads boards only through those open tabs.
- Anonymous problem reports: when reports are on, your assistant can send Irakasi anonymous problem reports.
If it does not connect
| What you see | What to do |
|---|---|
| "Irakasi could not connect this tab to your AI app." | Ask your assistant to use Irakasi, then choose Connect to local server again. If it still fails, quit and reopen your AI app. |
| Waiting for the local server | Ask your assistant to use Irakasi now. Irakasi keeps waiting for up to a minute. If nothing happens, check that the server is added to your AI app. |
| "Your local board MCP server is out of date. Quit and reopen your AI app to update it, then connect again." | Quit and reopen your AI app, then connect again. |
| Waiting for an AI app does not change | Ask your assistant to use Irakasi, or reopen your AI app. |
| One of your AI apps cannot reach Irakasi after an update | If you use Irakasi from several AI apps, quit and reopen all of them so they run the same version. If it still fails, check that their server setups allow the same folders. |