MCP. Connect your tools.
Plooi speaks the Model Context Protocol (MCP), so a method on your canvas can reach a tool that lives somewhere else — file an issue, read a project, search a catalog. You connect a tool once under Settings → Connections, and from then on any MCP method in any project can use it.
Closed Alpha. MCP works, and it is young. Which tools you can connect is curated by Plooi and grows one provider at a time — see Which tools you can connect.
The five pieces
Worth keeping apart, because they fail in different ways:
| Piece | What it is |
|---|---|
| Catalog | The set of tools Plooi is able to reach. Curated — there is no field anywhere for your own address. |
| Connection | Your link to one of them, pointed at one target. It belongs to you alone; nobody else on your team inherits it. |
| Sign-in | How the tool knows it is you: a token you paste, a sign-in at the provider, or nothing at all. |
| Tools | The operations that server offers. The list comes from the server itself, so it is always what that server actually does. |
| Export | The one direction that writes to the outside world, and the only one that keeps a ledger so it cannot happen twice. |
The call runs on the server
Your browser never talks to an MCP server and never holds a credential. It
names a connection and an operation; the mcp-host edge function loads the
address from the catalog row, decrypts your credential for that single call,
runs a real MCP handshake over JSON-RPC 2.0 (initialize, then tools/list or
tools/call), and hands back the result.
The address is never something the browser sent. That is the whole reason the transport sits on the server rather than in the page.
Adding a connection
- Open Settings → Connections.
- Pick an entry under Choose a tool…. Its description and a link to the provider’s own docs appear underneath.
- Fill in What it should work on — the page, repository or project this tool should act on. It is required, and it is part of what identifies the connection.
- Authenticate, which depends on the tool:
- Access token — paste one. Plooi checks it against the tool live before storing anything, then encrypts it.
- Sign in with … — the page hands you over to the provider and brings you straight back. Plooi never sees your password, only a token the provider issues for this one tool.
- Nothing — some tools answer without a credential.
- Press Connect. The connection appears in the list above the form with a Connected badge.
Screenshot placeholder. A shot of the Connections tab — one connected tool, one needing a reconnect — belongs here and has not been taken yet. The steps above are complete without it.
What “target” means
The target is not an address Plooi calls. It is passed to the tool as an argument and says which thing to work on; the address Plooi connects to always comes from the catalog entry instead.
Because the target is part of a connection’s identity, you can connect the same tool twice — one connection per project, per repository, per file — and pick between them on the canvas.
Which tools you can connect
The catalog decides, not this page. What appears under Choose a tool… is exactly the set switched on for your environment at that moment, and it can change without a release. If something below is missing from your list, it is not switched on yet.
Plooi ships catalog entries for:
| Tool | What the entry is for |
|---|---|
| Atlassian | Transfer user stories from the canvas into Jira, and read Confluence context back. |
| Figma | Send canvas work to a Figma file and import its frames back. |
| GitHub | Turn canvas output into issues, and read repository context onto the canvas. |
| Hugging Face | Search models, datasets and Spaces from the canvas. No credential required. |
| Linear | Push user stories and issues into Linear, and pull existing ones onto the canvas. |
| Notion | Write canvas results into a Notion page or database, and read briefs back. |
| Sentry | Pull real error and issue data onto the canvas as research input. |
Figma is switched off, and not because anything is missing on Plooi’s
side. Figma accepts only clients listed in its own MCP catalog and turns
everyone else away with 403 Forbidden during client registration — measured,
repeatedly. Plooi is applying for a listing; until that is granted the entry
stays off rather than offering a sign-in that cannot finish. Separately,
writing to a Figma file needs a Full or Dev seat on a paid Figma plan, per
person.
Why you cannot type your own address
There is no field for one, and that is an answer rather than a gap. Whatever address went in there, Plooi’s own servers would be the ones connecting to it, in your name. Letting that be free text means running a fetcher for anyone who asks.
This was genuinely open for a while and is now settled: the curated catalog is the whole set, and only Plooi adds to it. Missing something you need? Ask — a new entry is a small piece of work, and it is measured against the provider before it is switched on.
When a sign-in expires
A connection carries one of three states:
| Badge | Meaning |
|---|---|
| Connected | The last call went through. |
| Needs reconnect | The tool rejected the credential. Nothing is broken on the canvas; the connection just needs authenticating again. |
| Disconnected | Stored, but not currently usable. |
Access granted by a sign-in does not last forever. Where the provider issued a refresh token, Plooi renews silently — triggered by the rejection itself, not by the stated expiry, because the stated expiry has been measured to outlive the actual access. Renewal gets exactly one attempt per call, so a credential that is genuinely dead fails fast instead of looping.
If renewal is not possible, the connection flips to Needs reconnect. Open Settings → Connections and sign in again; your target and its history stay where they are. A call that succeeds flips the badge back to Connected on its own — you do not have to clear it.
What Plooi can see
Your credential is encrypted per connection with AES-256-GCM under a key derived for that row, from a master secret held in Supabase Function secrets rather than in the database — the same pipeline as your model keys, described in Bring your own key. Only server-side code with service-role rights writes or reads it; your browser gets a short hint and never the secret, never the refresh token, and not even the tool’s address. Plooi connects only to addresses standing in its own catalog, so nothing you type can steer where its servers reach; what a tool sends back is stripped of anything credential-shaped before it reaches your screen, the logs or error reporting; and calls are rate-limited per person, with writes to the outside held tighter than reads. Disconnecting deletes the row and the encrypted credential with it, which does not revoke anything at the provider — do that in the provider’s own settings.
On the canvas
Two methods use a connection. Both are free: an MCP call costs no credits.
- MCP Connection — calls one tool and puts the answer on the canvas, where it travels on to the next method. You pick the connection, pick a tool the server itself reports, and pass arguments.
- MCP Export — sends pinned user stories out as issues, and remembers what already went so a second run cannot file the same story twice.
Common questions
Can my teammates use my connection? No. A connection belongs to the person who created it, and every call checks that the caller owns it. Sharing a project does not share your credential — each person connects their own.
Why would I connect the same tool twice? Because the target is part of the connection. One Linear connection per team space, one repository connection per repository, and you choose between them on the canvas.
Does an MCP call cost credits? No. Neither calling a tool nor exporting draws from your balance.
What happens if I run an export twice? Nothing new. Every export is written to a ledger keyed by story and target, and the database — not the app — enforces one issue per story per target. Two runs at the same moment still produce one issue; a story that already went shows you its issue key instead.
Why can I not see MCP Export? It rolls out behind a switch, so it may not be turned on for your environment yet. Methods that write to someone else’s issue tracker are opened deliberately rather than as a side effect of a deployment.
A tool I need is not in the list. Can I host my own? Not today, and not by design accident — see Why you cannot type your own address. Tell us which one; adding a catalog entry is the path.
Is my data sent to these tools? Only what a method explicitly passes as arguments, and only when you run it. Plooi does not sync a canvas to a connected tool in the background, and nothing leaves without a run you started.