Start here

Connect Claude & other agents

Plainpaper talks to your agent over MCP, the open standard AI agents use to connect to tools. There are two ways in: claude.ai connects through Claude's connector directory, and everything else (Claude Desktop, Claude Code, any MCP-compatible agent) connects with a token you mint once.

How the connection works

Every connection ends at the same address:

https://app.plainpaper.io/mcp

What differs is how your agent proves who it is. On claude.ai, that's an OAuth sign-in through the connector directory, with no token involved. Everywhere else, it's an agent token: a credential you mint once on the Agents page in the app and paste into your client. Tokens are workspace-scoped. Each one belongs to exactly one workspace, so an agent holding it sees only that workspace's boards. There's no integration project hiding here: mint, paste, done. The connection also carries the agent's identity, so every card your agent creates is labeled with its name and the board always shows who made what.

Connect on claude.ai

On the Claude website, Plainpaper is a connector like any other. Go to Settings → Connectors → Browse connectors, search "Plainpaper", click Connect, and sign in with your Plainpaper account once. From then on, Claude can see your boards in any chat where you enable the connector. The install guide walks through it click by click.

i

Agent tokens don't work on claude.ai. The website's connector surface is OAuth-only, so a pp_ token has nowhere to go there. Tokens are for Claude Desktop, Claude Code, and other MCP clients; claude.ai uses the connector instead.

Connect in Claude Desktop and Claude Code

1

Mint a token

Open the Agents page in Plainpaper and mint a new token. Give it a label you'll recognize later: "Claude Desktop, laptop" beats "token 3". Copy it.

2

Add Plainpaper to your client

In Claude Desktop or Claude Code, add Plainpaper as a custom (remote) MCP server: the endpoint above, plus your token. The Agents page shows a mint → configure → test walkthrough for each client, so follow along there. It always matches the current version of each app.

3

Test it

Ask your agent to check in; the prompt is below. If it names your workspace, you're connected.

Other agents

Tokens aren't Claude-specific: they work with any MCP-compatible client. When you mint one, you tag which agent it's for: Claude, OpenAI, Gemini, Mistral, DeepSeek, or "other" with a name you type yourself. The tag shows on each token's row, so a list of connections stays legible. Whatever the vendor, the agent gets the same abilities: read boards, draft cards, propose actions for your approval.

Managing tokens

The Agents page is also where tokens live afterwards:

  • Label: every token carries the name you gave it.
  • Revoke: kill a token anytime; the agent using it is disconnected on the spot.
  • View again: lost the token before pasting it? Open the row menu and show it again.
  • Last used: each row shows when the token last connected, so stale ones are easy to spot and prune.
!

Treat a token like a password. It carries editor authority over its workspace: anyone holding it can read and write your boards. Don't paste it into shared documents, and mint one token per agent or tool. When something needs revoking, you cut one connection instead of all of them.

Test the connection

Whichever route you took, verify it the same way. Ask your agent to check in:

Copy-paste prompt
Check my Plainpaper connection. Which workspace are you connected to, and which boards can you see?

A working connection answers with your workspace's name and its boards. From there, jump to the Quickstart to give your agent its first real job.

Troubleshooting

The agent sees the wrong boards
The token belongs to another workspace. Tokens are workspace-scoped, and each workspace mints its own. Switch to the workspace you meant, mint a token from its Agents page, and revoke the old one.
claude.ai won't take my token
It can't; that surface is OAuth-only. Use the connector directory instead, and keep the token for Desktop, Code, or another MCP client.
A tool seems missing
Clients cache the tool list they saw at connect time. Reconnect Plainpaper, or refresh the client's tool list, and the full set comes back.

Still stuck? Run a fuller diagnostic and read what comes back:

Copy-paste prompt
Run a Plainpaper connection check: name the workspace you're connected to, list the boards you can see, and list the Plainpaper tools you have available right now.