Connect Plot to an AI assistant

Plot connects to AI assistants through its official MCP (Model Context Protocol) server. Once connected, your assistant can find, create, and update tasks, projects, documents, areas, and comments in your Plot workspace, all from a conversation.

Choose your assistant

Each guide covers setup, example prompts, how to disconnect, and fixes for common problems.

Connection details

Every assistant uses the same server:

https://mcp.plot.app/mcp

The server uses Streamable HTTP and OAuth. You never copy an API key. The first time your assistant connects, Plot opens in your browser:

1. Sign in to Plot.
2. Choose the workspace the assistant should use.
3. Review the app name and the permissions it requests.
4. Select Authorize.

What your assistant can do

Once connected, your assistant can:

• Read tasks, projects, documents, areas, labels, and task statuses.
• Create and update tasks, including subtasks and dependencies.
• Create and update documents and areas.
• Search across your workspace.
• Read and add comments.
• Read recent activity and your inbox.

Plot applies your normal permissions to every request. Your assistant can only see and change what you can see and change in Plot.

Plugins and skills

Plot also ships a plugin for Claude, Codex, Cursor, and Grok. The plugin adds the Plot server and a managing-plot skill. The skill teaches the assistant how to work in Plot:

• Move a task to In Progress when it starts, and to Review when it finishes.
• Record blockers as a status and a task dependency.
• Study the area's existing projects before it plans a new one, and match their naming, size, labels, and statuses.
• Keep plans and PRDs in Plot documents linked to their tasks.
• Link every Plot item it mentions.

Assistants that connect without the plugin still get the same guidance from the Plot server. Each assistant guide shows how to install the plugin.

Other MCP clients

Any client that supports remote MCP servers with OAuth can connect to https://mcp.plot.app/mcp. Add it as a Streamable HTTP server, then sign in when the client asks.

If your client only supports local servers, run the server through mcp-remote:

{
  "mcpServers": {
    "plot": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.plot.app/mcp"]
    }
  }
}

To install the plugin in Grok Build, run:

grok plugin marketplace add plot-hq/agent-plugins
grok plugin install plot --trust

Troubleshoot common issues

These fixes apply to every assistant.

The assistant is using the wrong workspace

A connection covers one workspace, chosen when you sign in. To use another workspace, disconnect Plot in your assistant, connect again, and pick the other workspace.

The assistant stopped working after a few weeks

Connections expire 30 days after you authorize them. Reconnect Plot in your assistant to sign in again.

The assistant says the connection is read-only

The assistant asked for read access only. Disconnect Plot and connect again. When Plot shows the requested permissions, check that write access is listed before you select Authorize.

The sign-in window doesn't open

Allow pop-ups for your assistant and for plot.app, then try again. Private browsing windows can block the sign-in cookie, so use a normal window.

A change didn't appear in Plot

Ask the assistant to read the task or document again. If a connection failed partway through a change, the change may have saved anyway. The Plot skill tells assistants to check before they try again, so they don't create duplicates.

Disconnect Plot

Remove Plot from your assistant to stop it from reading or changing your workspace. Each assistant guide shows where to do this. The connection also ends on its own 30 days after you authorize it.

Privacy

Your assistant sends requests to mcp.plot.app, which calls the Plot API on your behalf. Plot keeps its access tokens on its own servers and never sends them to the assistant. Data the assistant reads from Plot is also covered by your assistant provider's privacy policy. See the Plot privacy policy.