plumo plays well with what you already use.
connectors built with the same care as the rest of plumo. minimal permissions, opt-in only, never noisy. and yes — your AI assistants can drive plumo directly through MCP.
plumo speaks AI, fluently.
a first-class MCP server, included in every plan. your claude, your custom agents, any MCP-compatible assistant — they all read and act on plumo as a teammate, never a screen-scrape.
plumo ships an MCP server (stdio + HTTP). claude, custom agents, and other assistants can list projects, add issues, log time, run sprint operations — permission-scoped, fully audit-logged.
connect claude.ai to plumo with one click. your conversations can read, draft, and update issues directly — with your permission, every time.
livea clean REST API and webhook subscriptions for everything plumo does. token-scoped, rate-limited softly, with a friendly developer portal.
livewhere your team already talks.
plumo whispers in slack — gentle digests, opt-in mentions, and the quietest "/plumo" command. notifications never push, only invite.
livetwo-way sync, gently. issues, statuses, comments. perfect for teams mid-migration — keep linear running while plumo takes over.
livepull requests, the quiet version. link PRs to issues, auto-close on merge, log time against branches. no spammy comments on your PRs.
livegoogle, gently.
your day, side by side. plumo reads your calendar and slots tasks between meetings — never overlapping, never pushy.
liveturn an email into a small thing to do — without leaving your inbox. a quiet "send to plumo" button, scoped to one message at a time.
liveattach files to issues without thinking about them. plumo links to drive, never copies — your permissions are the ones that count.
liveminimal permissions, always.
every integration uses the smallest scope that works. read-only by default. you can revoke any connection in one click, and we log every AI action in a quiet audit trail you can review anytime.