NewCapy V2 is here
Integrations

Your tools, wired together

Capy connects to GitHub, Slack, Linear, Vercel, Tailscale, and MCP servers — so an issue can become a reviewed, previewed, merged PR without anyone re-explaining context between tools.

Get startedView integrations
Capy asleep on a giant cursor

Six connections, one workflow

Each connection covers a different stage of the same workflow: where code lives, where work is tracked, where the team talks, where changes go live, where private services run, and where any other tool plugs in.

GitHub

Where the code ships. The Capy GitHub App clones your repos and works on isolated branches — your default branch only moves through your own merge process.

See the GitHub workflow

Slack

Where the team talks. Tag @Capy in any channel to turn a thread into a running task — it reads the conversation for context and reports back in the same thread.

See Capy in Slack

Linear

Where work is tracked. Delegate an issue to Capy and it lands in the right project, on the right base branch, with the issue attached as context.

See the Linear flow

Vercel

Where changes go live. When Vercel posts a preview URL on a PR, Capy pins it next to the diff so reviewers can open the running app mid-review.

See preview reviews

Tailscale

Where your private services live. Agent machines join your tailnet as ephemeral tagged nodes at boot, reaching internal databases and staging APIs under your own ACLs.

Read the Tailscale docs

MCP

Where everything else plugs in. Connect remote HTTP or local stdio MCP servers, org-wide or per project, and agents discover and call their tools while they work.

Read the MCP docs

Work that crosses tool boundaries

A single task can read an issue, write code, post an update, and surface a preview — because every hop is already connected before the agent starts.

Across your stack

  • Issues become branches and PRs
  • Progress updates in Slack threads
  • Boards move as work completes
  • Docs and specs pulled as context
  • Preview deploys on every change
  • Status synced across tools
Puzzle piece clicking into place

FAQ

Connections, permissions, and what happens when things change.

How do I connect an integration?+
GitHub, Slack, Linear, and Vercel connect from Settings → Integrations over OAuth, with no tokens to manage. Tailscale connects from the same page with an OAuth client ID, secret, and tag from your tailnet. MCP servers are configured under Settings → MCP servers, with OAuth, a header token, or environment variables depending on the server.
Can I limit which repos or channels agents access?+
Yes. Permissions are granular per integration — restrict by repository, Slack channel, or Linear project, and adjust the scope later.
What happens if an integration disconnects?+
Agents handle the disconnection, you get notified, and reconnecting is one click. No work is lost in between.
Are more integrations coming?+
Yes — Jira, Notion, and more are in progress. Join our Discord to vote on what ships next.
Can I build my own integration?+
Yes. Every plan includes API access: create an organization API key under Settings → API to start threads, run reviews, and read results from your own tools. See the API reference on docs.capy.ai.

Wire up your stack today

Connect GitHub, Slack, Linear, Vercel, Tailscale, and your MCP servers once — every agent you run uses them from then on.

Get startedContact Sales
Capys leaping through comic panels