Pixeltable Cloud MCP
Connect an MCP client to the Pixeltable Cloud organization you select during WorkOS AuthKit sign-in, or, if you select none, to the organizations you belong to. The hosted server lists databases, services, catalog entries, and secret names, reads table schemas, up to 25 rows per call, the cells where a computed column failed, table history, and recent logs. It can also start, stop, and restart databases and services, retry a change that failed, and set secrets. Stopping, restarting, and setting a secret return a preview first, and act only when called again with confirm: true. It cannot delete anything, run arbitrary queries, or invoke services.
New to Pixeltable Cloud? Signing up through your MCP client gives it every tool plus create_organization: tell your agent the name you want and confirm it (it cannot be changed later). The other tools use the new organization right away, with no new sign-in. If you belong to several organizations and chose none at sign-in, the agent names one with each tool's org argument.
Add ?read_only=true to the endpoint for the read tools only, and ?db=<name> to limit a connection to one database, for example https://www.pixeltable.com/mcp/cloud?read_only=true&db=main.
Connect
Remote Streamable HTTP endpoint: https://www.pixeltable.com/mcp/cloud
The Pixeltable plugin and Skill do not configure this server. Add it with the steps below. If your client already lists pixeltable-cloud, connect that entry instead of adding a second one.
Claude
In Claude (claude.ai and Claude Desktop), add Pixeltable Cloud from the Claude directory, then connect it and complete browser sign-in. On Team and Enterprise plans, an Owner adds it for the organization first.
Claude Code
claude mcp add --transport http pixeltable-cloud --scope user https://www.pixeltable.com/mcp/cloudRun /mcp in Claude Code, select pixeltable-cloud, and complete browser sign-in.
Cursor
Install it with Add to Cursor, or add this entry to ~/.cursor/mcp.json, preserving your other servers. Then connect it in Cursor and complete browser sign-in.
{
"mcpServers": {
"pixeltable-cloud": {
"url": "https://www.pixeltable.com/mcp/cloud"
}
}
}Other MCP clients
Add the same HTTP URL as a remote MCP server and follow its OAuth connection flow. The server advertises OAuth resource metadata and a server card.
Disconnect
To disconnect, delete the pixeltable-cloud entry from the client's MCP settings. In Claude, remove the connector under Customize > Connectors. In Claude Code, claude mcp remove pixeltable-cloud also deletes the tokens it stored. Where the client has a logout command, run it with the server name: codex mcp logout, opencode mcp logout, or devin mcp logout. Gemini CLI's mcp-remote bridge keeps tokens in ~/.mcp-auth, so delete that folder too.
Disconnecting deletes the client's copy of the tokens. It does not revoke the authorization, and Pixeltable has no page that lists or revokes MCP authorizations.
Did the sign-in page go straight to consent for a different account? The browser is still signed in to that account. Open https://www.pixeltable.com/logout to sign out, then connect again from the client. If you already allowed access, disconnect first (above): the client keeps that account's tokens.
Guides
- Cloud MCP tools: Every advertised tool, with parameters, read-only and confirm flags, and the no-organization pair.
- Connect Cursor to Pixeltable Cloud: Merge the hosted endpoint into ~/.cursor/mcp.json and complete AuthKit sign-in.
- Give Claude access to images with MCP: Cloud MCP returns JSON, not pixels. Run a vision column, then let Claude read that text through get_table_rows.
Choose the right Pixeltable MCP
- Cloud MCP: this authenticated server for your hosted Cloud data and operations.
- Docs MCP: public documentation search, without Cloud data access.
- Developer MCP: the local stdio server for catalog inspection, queries, and REPL tools against a local or Cloud database.
Questions: contact us. See our privacy policy and terms.