---
title: "Connect Cursor to Pixeltable Cloud"
description: "Add the hosted Pixeltable Cloud MCP server to Cursor, complete AuthKit sign-in, and name your first organization from Cursor if you have none."
url: "https://www.pixeltable.com/developers/mcp-cloud/connect-cursor"
---

# Connect Cursor to Pixeltable Cloud

The hosted Pixeltable Cloud MCP endpoint is `https://www.pixeltable.com/mcp/cloud`. Cursor talks to it as a remote Streamable HTTP server. The Pixeltable plugin and Skill do not configure this server. If Cursor already lists `pixeltable-cloud`, connect that entry instead of adding a second one. Broader Cursor setup (Skill, plugin, docs WebMCP) lives on [/agents/cursor](https://www.pixeltable.com/agents/cursor).

## 1. Merge the server into `~/.cursor/mcp.json`

Keep any servers you already have. Add this entry:

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

Read-only tools only: set `url` to `https://www.pixeltable.com/mcp/cloud?read_only=true`. One database: add `&db=main` (or that database's slug).

## 2. Connect and complete AuthKit sign-in

In Cursor, connect `pixeltable-cloud` and finish the browser sign-in. The organization you pick is the one the tools can read and operate.

## 3. If you have no organization yet

The tools say to call `create_organization` first. Tell Cursor the name you want (it is permanent) and confirm the preview. The other tools act in it at once, on the same connection, with no new sign-in.

A read-only connection (`?read_only=true`) hides `create_organization`. Create the organization at https://www.pixeltable.com/onboarding?from=mcp instead; the tools then act in it on the same connection.

## 4. Confirm the session

Call `get_current_organization`. It returns the org slug, default database, and the site serving this server. The full tool list is on [/developers/mcp-cloud/tools](https://www.pixeltable.com/developers/mcp-cloud/tools).

