Connecting your tools

An integration is a connection that lets your assistant use an outside tool or service on your behalf — reading from it, writing to it, or both. Once a tool is connected, you can simply ask in chat ("pull this week's open issues from Linear", "create a Stripe payment link") and your assistant handles the rest.

The easiest way: just ask your assistant

You don't have to set anything up by hand. Tell your assistant what you want to connect — "connect my Gmail", "hook up our Stripe account", "pull data from our 1C" — and it figures out the best way to do it and walks you through anything it needs.

Some tools are ready-made: your assistant connects them from a built-in Library in a tap or two. Others — like Gmail and the rest of Google, your accounting system, or an in-house service — it connects by setting up a custom connection for you behind the scenes. Either way you just ask in plain language: if a sign-in is needed it hands you a link to approve access (it never sees your password), and if a key is needed it asks you for it right in the chat.

So the short version is: don't hunt for settings — just ask. The rest of this page covers the Library and the Settings screen, for when you'd rather browse and connect things yourself.

Beta: Managing integrations is currently a beta feature, so the Integrations settings section is hidden until you turn it on under Settings → Preferences → Beta features. See Beta features. (The Integrations sidebar section, which also lists your workspace scripts, stays visible.)

Plank's integrations are built on a standard called MCP (Model Context Protocol). You don't need to know anything about MCP to use them — think of each one as a doorway between your assistant and a service you already use.

Where integrations live

You manage integrations in two places, and they stay in sync:

• Settings → Integrations — a visual list of what's connected, plus a Library of ready-made integrations you can add with one tap.
• In chat — you can ask your assistant to find and set up an integration for you, without leaving the conversation.

Both routes do the same thing under the hood, so use whichever feels natural.

The Library: ready-made integrations

The Library (under Settings → Integrations) is a collection of pre-built integrations for popular services. Each one already knows how to connect — you don't have to configure anything technical.

Examples available in the Library include Notion, Linear, Stripe, Sentry, PostHog, Supabase, and Vercel, among others. Use the search box at the top of the Library to filter by name, and the category chips to narrow by type.

Each Library card shows the integration's name, a short description, and what (if anything) it needs from you to connect.

Adding one from Settings

1. Open Settings → Integrations.
2. Find the integration you want in the Library (search if needed).
3. Tap Set Up on its card.

What happens next depends on how that service authenticates:

Once everything's in place, the integration shows Ready in chat — that's your cue that the assistant can use it.

If something still needs your attention, the card tells you in plain language — for example Needs account connection or Needs credentials. Tap the labelled button to pick up where setup left off.

Authorizing a connection (sign-in flow)

Many integrations connect by signing you in to the service, rather than asking for a key. When you tap Connect Account, Plank opens the service's own sign-in page in a new tab. You log in there and approve the access — Plank never sees your password. After you approve, you can close that tab; Plank detects the connection and updates the integration to Ready in chat.

If a connection ever stops working, open the menu on the integration and choose Reconnect to sign in again.

Adding one from chat

You can also set up an integration just by talking to your assistant — no need to open Settings. For example:

"What integrations can I connect?"

"Set up Notion for me."

Your assistant can browse the same Library, create the integration, and walk you through finishing setup. If the service needs you to sign in, it will hand you a link to do so; if it needs a key, it will ask you for it in the conversation. Either way it's the same secure setup as the Settings flow, just guided by chat.

For assistants: add it as an integration, not as a config file edit

Some MCP servers can also be wired up by writing them straight into the workspace's opencode.json. That works, and it is the wrong door. An MCP server added that way does not appear in Settings → Integrations, so nobody can see it, switch it off, or delete it without editing the file again — and it still gets connected every time the workspace's assistant starts up.

Create the integration instead (Settings, or by asking in chat, as above). Then it is listed, it can be turned off in one click, and removing it actually removes it.

If a server is already configured in the file, Plank leaves it alone — it is usually something you asked for and deleting it would break it — but it will tell you that it is not managed, and it stays invisible in Settings until it is re-added properly.

Who can use it, and where: scope

When you add an integration you choose its scope — how widely it applies. Plank offers three:

You can change an integration's scope later from its menu. Team integrations are managed by workspace owners and admins.

Removing an integration

Open the menu on any integration and choose Delete. This removes the connection and its setup. (Removing an integration doesn't delete anything in the outside service — it just disconnects Plank from it.)