Skip to content

Shared tools.
Personal control.

Connect your team’s tools once and every agent can use them. Your own calendar and accounts stay yours, used only when you ask.

Connect once for the team.

An admin signs in once, and every agent gets the tool. Nothing to repeat per agent or per channel.

  • See who connected each tool.
  • Members see the list, not the settings.
  • Add anything that speaks MCP.

Your accounts stay yours.

Connect your own calendar, notes and recordings. Agents use them only when you ask, and nobody else can read them.

  • You choose which agents may use them.
  • Colleagues reach their own accounts, never yours.
  • Admins can’t read or switch them on.

Work and private, side by side.

Connect a work calendar and a private one, pick a default, and name the other when you need it.

  • Add accounts without replacing one.
  • Unsure which account? The agent asks.

Always the person who asked.

When you ask, the agent acts for you, even after it hands work to a colleague. “My calendar” always means yours.

  • Your own accounts take over in your requests.
  • Everyone else keeps using the team’s.

A GitHub identity of their own.

Agents push code under their own GitHub identity, limited to the repositories you choose.

  • Every commit shows which agent made it.
  • Only a GitHub owner can connect it.
  • Disconnect any time, access revoked.

A browser that never sees your password.

When a site needs a sign-in, the agent stops and asks. You type it yourself, and saved sign-ins stay in an encrypted keychain.

  • Banks and payment sites are off limits.
  • Paying, sending or publishing always asks first.
  • You choose who may use a saved sign-in.

Two kinds of connection.

The difference is who owns it.

Shared with the team

Set up once by an owner or admin.

  • Used by every agent in the workspace.
  • Shows who connected it.
  • Admins manage it; members see it.

Personal to you

Connected by you, from your settings.

  • Used only for your requests.
  • You choose which agents may use it.
  • Several accounts, one default.
  • Private from admins, gone when you leave.

The tools your team already uses.

From project tracking to payments, plus custom MCP for anything else.

Available now

  • Granola
  • Notion
  • Linear
  • GitHub
  • Framer
  • Google Drive
  • Polder
  • Vercel
  • Google Calendar
  • Search Console
  • Stripe
  • Cirrux
  • Custom MCP

Coming next

  • Microsoft Teams
  • Sanity
  • Microsoft 365
  • Figma

Questions, answered.

Can an admin see my calendar?

No. Personal connections are yours alone, and what agents read from them stays out of shared spaces.

What if a colleague asks the same agent?

The agent uses that colleague’s own accounts. They never reach yours.

Can I connect a tool that is not on the list?

Yes. An admin can add any tool that offers an MCP server.

Do agents ever see my passwords?

No. You type them into a secure form or the browser yourself, and agents never see them.

What happens when someone leaves the team?

Their personal connections are disconnected. Team tools stay connected.

Keep exploring.

Agents as team mates.

Get agents equipped with advanced skills and capabilities. Give them your methods, client knowledge and approved tools.

Meet the agents

Make the work your clients need.

Create briefs, strategies, website drafts and campaign assets. Shape, review and refine the work together.

Docs & sites

Work together, in the open.

Bring your team and agents into the same conversation. Share context, ask questions and build on each other’s work.

Mac, web & mobile

Bring your team to Bureau.

Download the Mac app or start in your browser. Try it free for 7 days, no card.