Connect your assistant

Pixalate works with any assistant that supports remote MCP servers over Streamable HTTP. The
setup is the same everywhere: one address, no key, and a browser sign in the first time.

https://mcp.pixalate.com/mcp

Name the server pixalate-mcp. There is nothing else to configure. If a client asks for an API
key, a token, or an Authorization header, leave those fields empty: Pixalate signs you in
through the browser, and a credential left in the configuration stops that from starting.

The steps for each client below come from that vendor's own documentation, linked in every row.

Clients with a full guide

These have their own page with the exact menu path.

Client	Guide
Claude, web and desktop	Connect Pixalate to Claude
ChatGPT	Connect Pixalate to ChatGPT
Cursor	Connect Pixalate to Cursor

Every client

Added in the app itself

No configuration file. You add Pixalate from inside the app and sign in.

Client	How you add it
ChatGPT our guide	Turn on developer mode in settings, add a custom app, and paste the URL.
Claude, web and desktop our guide Claude Desktop config file (mcp-remote bridge)	Open Connectors under Customize, add a custom connector, and paste the URL. On desktop you can also add the server to your config file through the `mcp-remote` bridge. On Team and Enterprise plans, the owner adds the connector under Organization settings. Members cannot add one themselves.
Gemini app	Open Connected Apps in settings, add a custom app, and paste the URL.
Microsoft Copilot Studio	Add an MCP tool to one of your agents and paste the URL.
Mistral Le Chat	Add a custom MCP connector in settings and paste the URL. Your admin enables it.
Notion AI	Add a custom MCP in settings and paste the URL. Business or Enterprise, and your admin enables it.
Perplexity	Add a custom connector in settings and paste the URL. Enterprise, and your admin enables it.
Raycast	Install an MCP server in settings and paste the URL. Needs Pro.
Replit Agent	Add an MCP server in settings and paste the URL.
Zapier	Add an MCP Client connection and paste the URL. Currently in beta.

Added by editing a configuration file

The address is the same everywhere. What differs is the key it goes under, and putting a correct address under the wrong key is the most common reason a setup does not connect.

Client	How you add it	Configuration key
Amazon Q Developer	Add the server to `mcp.json`.	`mcpServers > type: http + url`
Amp	Add it with a single command.	`CLI / amp.mcpServers > url`
Claude Code	Add it with a single command.	`CLI: --transport http`
Cline	Open the Remote Servers tab in settings and paste the URL.	`mcpServers > type: streamableHttp + url`
Codex CLI	Add it with a single command.	`[mcp_servers.<name>] url`
Continue	Add the server to `config.yaml`.	`mcpServers[] > type: streamable-http + url`
Cursor our guide	Use the one-click install link, or add the server to your config file.	`mcpServers > url`
Gemini CLI	Add it with a single command.	`mcpServers > httpUrl`
GitHub Copilot in VS Code	Add the server to `.vscode/mcp.json`. Tools appear in Agent mode.	`servers > type: http + url`
Goose	Run `goose configure` and add the server.	`extensions > type: streamable_http + uri`
JetBrains AI Assistant	Add an HTTP server in settings and paste the URL.	`mcpServers > url`
Kiro	Add the server to `mcp.json`.	`mcpServers > url`
Visual Studio Code	Add the server to `mcp.json`.	`servers > type: http + url`
Warp	Paste the server JSON in settings.	`<name> > url`
Windsurf	Add the server to your config file.	`mcpServers > serverUrl`
Zed	Add the server to `settings.json`.	`context_servers > url`

Questions about a specific client

ChatGPT: I cannot find where to add a connector

Custom connectors only appear once developer mode is switched on. Turn it on in settings first, then add the connector and paste the URL.

Claude, web and desktop: I added the connector but Claude Code cannot see it

Claude Code is a separate product and connects separately, with its own command. Adding a connector in Claude on the web or the desktop app does not carry across.

Cursor: Should I use the install link or edit the config file?

Either. The install link writes the same configuration for you. Edit the file directly if you keep your editor config in version control or want to see exactly what was added.

GitHub Copilot in VS Code: I use GitHub Copilot and the tools do not appear

GitHub Copilot only exposes MCP tools in Agent mode. Switch the Copilot chat view to Agent mode and the tools appear. In Ask or Edit mode they will not, and nothing about the configuration is wrong.

In Agent mode and still nothing? I connected but I see no Pixalate tools

The configuration shapes

Most clients want the address under a key. Three shapes cover nearly all of them:

Most editors, using url:

{
  "mcpServers": {
    "pixalate-mcp": {
      "url": "https://mcp.pixalate.com/mcp"
    }
  }
}

VS Code and GitHub Copilot, note servers rather than mcpServers, and the explicit type:

{
  "servers": {
    "pixalate-mcp": {
      "type": "http",
      "url": "https://mcp.pixalate.com/mcp"
    }
  }
}

Windsurf, note serverUrl rather than url:

{
  "mcpServers": {
    "pixalate-mcp": {
      "serverUrl": "https://mcp.pixalate.com/mcp"
    }
  }
}

Check the table above for your client's exact key. Copying the address into the wrong key is the
most common reason a correct setup does not connect.

A note on three clients

JetBrains AI Assistant, Cline and Continue document Streamable HTTP support but do not document
an OAuth sign in flow. Pixalate requires one. If the browser sign in does not start on those
clients, a local bridge is the documented workaround, and the vendor pages linked above cover it.

If your client is not listed

It will still work if it supports remote MCP servers over Streamable HTTP. Give it the address
above, choose OAuth if it asks how to authenticate, and leave any key or token field empty. If
it offers a choice of transport, choose Streamable HTTP rather than SSE.

Check that it worked

Ask your assistant:

What Pixalate reports can I run?

If you get report names back, you are connected and your account is enabled. An empty tool list
after a successful sign in means your account has not been enabled yet, which your Pixalate
account manager can arrange.

Reviewer note, not for publication: the client tables above are generated from the shared
source, mcp-site/src/clients.json, by _gen_clients.py. Do not hand-edit them. Send changes to
the website agent, who owns that file, and regenerate.

Sourcing: every client in the shared source is currently unverified, meaning nobody has tested
the connection against a live client. Rather than repeating the agreed sentence in 28 table
rows, it is stated once above the tables and each row links the vendor documentation it came
from. Confirm with the website agent that this satisfies the identical-surfaces requirement,
since their cards carry it per client.