MCP

Connect an assistant

Setup for Claude Code, Claude.ai, Cursor, and anything else that speaks MCP.

Claude Code

claude mcp add --transport http pxb https://www.pxb.app/mcp

Then run /mcp, choose pxb, and Authenticate. Your browser opens on Pixelbase: pick the companies and permissions, and you're connected.

An assistant with no browser

An agent running in a sandbox, or on a server, can sign in with the device flow (RFC 8628) instead. It asks POST /api/oauth/device-authorization for a code, shows you a link and a code like BCDF-GHJK, and polls the token endpoint while you open the link on any device, sign in, check the code matches and approve. Only apps that registered the urn:ietf:params:oauth:grant-type:device_code grant can start one.

No Pixelbase account yet

An agent can start one for you: POST /api/public/v1/signup with the company to create, and your name and mobile number if it knows them. It gets a link for you — on it you check the details and fill in the rest, add a card and confirm a code texted to your phone, then approve the agent — and polls for its tokens the same way. It never sees the card or the code. See the setup page for agents.

Claude.ai and Claude Desktop

Under Settings → Connectors, add a custom connector with the URL above, then connect it. The same Pixelbase page opens.

Cursor, VS Code, and other clients

Add the server to the client's MCP configuration; any client that supports MCP sign-in will open the Pixelbase page the first time it connects:

{
  "mcpServers": {
    "pxb": { "type": "http", "url": "https://www.pxb.app/mcp" }
  }
}

Several companies

One connection can cover several of your companies, each with its own permissions; the assistant names the company on each call. If you'd rather keep them apart, add the server twice under different names — pxb-acme, pxb-beta — and connect each to one company.

A client that can't sign in

Use an API token instead. Create a client on the Dev Tools page with the scopes you want, exchange its credentials for a token, and send it as a header:

curl -s -u "$PXB_CLIENT_ID:$PXB_CLIENT_SECRET" \
  -d grant_type=client_credentials \
  https://www.pxb.app/api/public/v1/oauth/token

{ "headers": { "Authorization": "Bearer $PXB_TOKEN" } }

Tokens minted this way last an hour and act as the employee who created the client. If you have the CLI, pxb auth handles the exchange for you.

Check it worked

Ask the assistant to call whoami. It answers with who it acts as, the companies it reaches, and each company's tools — reads and writes apart. If a list is shorter than you expected, edit the connection under Dev Tools → MCP.

Tools →