---
title: "Pixeltable Cloud MCP"
description: "Connect Claude Code, Cursor, and other MCP clients to read and operate your Pixeltable Cloud databases, services, tables, and logs."
url: "https://www.pixeltable.com/developers/mcp-cloud"
---

# Pixeltable Cloud MCP

Connect a remote Streamable HTTP MCP client to https://www.pixeltable.com/mcp/cloud. WorkOS AuthKit sign-in selects the Cloud organization; if it selects none, each tool acts in the account's only organization, or the one its `org` argument names. The hosted server lists databases, services, catalog entries, and secret names (never values), reads table schemas, up to 25 rows per call, the cells where a computed column failed, table history, and recent logs. Write tools are `start_database`, `start_service`, `stop_database`, `stop_service`, `restart_database`, `restart_service`, `retry_change`, and `set_secret`. Starting a database or a service and retrying a failed change act at once. 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.

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`.

The [Pixeltable plugin](https://github.com/pixeltable/pixeltable-skill) 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](https://claude.ai/directory/pixeltable-cloud-mcp), then connect it and complete browser sign-in. On Team and Enterprise plans, an Owner adds it for the organization first.

## Claude Code

```bash
claude mcp add --transport http pixeltable-cloud --scope user https://www.pixeltable.com/mcp/cloud
```

Run `/mcp` and complete browser sign-in.

## Cursor

Install it with [Add to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=pixeltable-cloud&config=eyJ1cmwiOiJodHRwczovL3d3dy5waXhlbHRhYmxlLmNvbS9tY3AvY2xvdWQifQ%3D%3D), or merge this entry into `~/.cursor/mcp.json`. Then connect it in Cursor and complete browser sign-in:

```json
{"mcpServers":{"pixeltable-cloud":{"url":"https://www.pixeltable.com/mcp/cloud"}}}
```

Other remote MCP clients can use the same URL. [OAuth resource metadata](https://www.pixeltable.com/.well-known/oauth-protected-resource/mcp/cloud) and the [server card](https://www.pixeltable.com/.well-known/mcp/cloud/server-card.json) describe discovery.

The [Docs MCP](https://docs.pixeltable.com/mcp) searches public documentation. The [local developer MCP](https://github.com/pixeltable/mcp-server-pixeltable-developer) runs stdio catalog, query, and REPL tools. For support, see [Contact](https://www.pixeltable.com/contact), [Privacy](https://www.pixeltable.com/privacy), and [Terms](https://www.pixeltable.com/terms).

## 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](https://www.pixeltable.com/developers/mcp-cloud/tools): every advertised tool, with parameters.
- [Connect Cursor to Pixeltable Cloud](https://www.pixeltable.com/developers/mcp-cloud/connect-cursor)
- [Give Claude access to images with MCP](https://www.pixeltable.com/developers/mcp-cloud/give-claude-access-to-images)

With no organization, the tools say to call `create_organization`. The other tools act in it at once, on the same connection, with no new sign-in. The organization includes database main, and create_organization returns the commands that deploy an app onto it.
