Connect the Workbench

The Shapes Workbench is a remote MCP server. Connect it to your AI client and the shape_workbench_* tools become available in your session.

Endpoint

https://shapes.pnbr.io/mcp

Authentication

The Workbench MCP accepts two kinds of credentials. Use whichever your client supports.

API key

Pass your Penumbra API key as a bearer token. It is the same pnbr- key the SDK uses, which makes it the simplest path and the right one for headless setups (CI, scripts).

export PENUMBRA_SHAPE_WORKBENCH_API_KEY="pnbr-..."

OAuth

Clients that support remote-MCP OAuth can connect with no key in their config. The server advertises its OAuth metadata, the client opens a browser consent flow, and the resulting token authorizes the session (the server requests the shapes.write scope so the draft-editing tools work). Use this for interactive desktop clients that prefer a login over a stored key.

Add it to your client

Claude Code
Cursor / JSON
Codex

claude mcp add --transport http shapes \
  https://shapes.pnbr.io/mcp \
  --header "Authorization: Bearer $PENUMBRA_SHAPE_WORKBENCH_API_KEY"

Add to your MCP config:

{
  "mcpServers": {
    "shapes": {
      "url": "https://shapes.pnbr.io/mcp",
      "headers": {
        "Authorization": "Bearer pnbr-..."
      }
    }
  }
}

[mcp_servers.shape_workbench]
url = "https://shapes.pnbr.io/mcp"
bearer_token_env_var = "PENUMBRA_SHAPE_WORKBENCH_API_KEY"
enabled = true
tool_timeout_sec = 120

Verify

List the tools to confirm the connection and your key:

curl -sS \
  -H "Authorization: Bearer $PENUMBRA_SHAPE_WORKBENCH_API_KEY" \
  https://shapes.pnbr.io/tools

Once connected, the shape_workbench_* tools appear in your client. Continue to Authoring.

​Endpoint

​Authentication

​API key

​OAuth

​Add it to your client

​Verify