MCP

PaneScale speaks the Model Context Protocol in both directions: it can call MCP servers you configure, and it is an MCP server other agents can call. Both live in Settings → MCP bridge.

#Managed connections

A managed connection is an MCP server that PaneScale starts and talks to itself, over standard input and output. Add one with Add connection: a name and the command that starts the server, for example:

npx -y @modelcontextprotocol/server-filesystem D:\Projects\shop

Check starts the server and lists its tools with their descriptions. In the same dialog you can try a tool by hand: pick it, enter its arguments as JSON and click Call — the result appears below. A checked connection is marked Checked.

Managed connections are available to workflow MCP steps and to other agents through the bridge.

#The bridge

The bridge is an MCP server inside PaneScale. With it, an agent in any pane — or any other MCP client on your computer — can work with your board.

#Connect a client

The bridge speaks MCP over HTTP at http://127.0.0.1:<port>/mcp and expects the token as a bearer header. The settings page shows the exact configuration to copy:

{
  "mcpServers": {
    "panescale": {
      "type": "http",
      "url": "http://127.0.0.1:41920/mcp",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

For Claude Code:

claude mcp add --transport http panescale http://127.0.0.1:41920/mcp --header "Authorization: Bearer <token>"

Use the port your settings page shows — it is usually 41920, or the next free one up to 41929.

#What the bridge offers

A typical use: an agent working in a pane creates follow-up cards for what it noticed but didn’t fix, and sends you a notification when it is done.

#Security

• Off until you turn it on.
• Listens only on 127.0.0.1, on a port from 41920 to 41929.
• Every request needs the bearer token; comparisons run in constant time. Treat the token like a password. Regenerate it at any time — old clients stop working immediately.
• Requests from web pages are refused, and request bodies are limited to 1 MB.
• Only plain POST requests are answered; there is no streaming endpoint.

The bridge can’t approve, merge, push or publish anything, and it can’t mark a task done — see Approvals.