IntegrationsClaude Code, Cursor & Others

Claude Code, Cursor & other clients

Connect Claude Code, Cursor, VS Code and any other MCP client to PanelWave, with browser sign-in or a personal access token.

Coding tools and other MCP clients connect to the same address as the hosted assistants:

https://mcp.panelwave.org/mcp

You can authenticate in two ways:

  • Browser sign-in (OAuth). The client opens a PanelWave page, you sign in and choose the permissions. Nothing to copy or store. Use this whenever the client supports it.
  • Personal access token. You create a token in PanelWave and put it in the client's configuration as an Authorization header. Use this for scripts, CI jobs and clients without sign-in support. See Access tokens & connected apps.

To work with files on your computer, such as uploading a folder of artwork, use the local bridge instead of the remote address.

Claude Code

Add the server:

claude mcp add --transport http panelwave https://mcp.panelwave.org/mcp

Start Claude Code, run /mcp, select panelwave and choose Authenticate. Your browser opens the PanelWave consent page. After you click Allow, Claude Code shows the server as connected.

Add --scope project to share the server with your team through the project's .mcp.json. Never commit a token; use sign-in for shared configurations.

Cursor

Add PanelWave to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project.

{
  "mcpServers": {
    "panelwave": { "url": "https://mcp.panelwave.org/mcp" }
  }
}

Cursor shows a Needs login button next to the server in its MCP settings. Click it to open the PanelWave consent page.

VS Code

Add PanelWave to .vscode/mcp.json in your workspace, or run MCP: Add Server from the command palette and choose HTTP:

{
  "servers": {
    "panelwave": { "type": "http", "url": "https://mcp.panelwave.org/mcp" }
  }
}

VS Code asks you to sign in to PanelWave the first time a tool is used.

Other clients

Any client that supports remote MCP servers over Streamable HTTP works. PanelWave supports current and older protocol versions, so clients from 2025 on connect too.

  • Sign-in: the client finds PanelWave's sign-in automatically. It can register itself, so leave client id and secret fields empty.
  • Token: send the header Authorization: Bearer pw_pat_… with every request.

To explore the tools by hand, run the MCP Inspector and connect it to the address above:

npx @modelcontextprotocol/inspector

Clients only show the tools your permissions allow. If a tool seems to be missing, check which permissions you granted, or ask the assistant to run pw_meta_explain_permissions for it.