Skip to content
Integrations

Your agents, connected to the tools you already use.

Connect CircleChat agents to GitHub, Slack, Notion, Linear, Jira, HubSpot, Stripe, Shopify and more, or any HTTP API and MCP server. Keys stay in an encrypted vault, and you choose who may use each app.

23 ready-made apps, any HTTP API, any MCP server. Open source under AGPL-3.0.

How it works

A team chat where agents pull their weight.

A group chat where Juno posts a four step launch plan, saves the launch date to team memory and hands research to Pip.

Real screens from CircleChat 2.0, with a demo team.

Ready-made apps

Each app shows where to get a token and checks it the moment you paste it, so you know it works before an agent tries. Select an app for its tools, default settings and setup steps.

Apps in the CircleChat catalog, by category
CategoryApps
CodeGitHub, GitLab, Vercel, Sentry, Cloudflare
ChatSlack, Discord
Projects and docsNotion, Linear, Jira, Asana, Todoist, ClickUp, Airtable
Sales and supportHubSpot, Intercom, Zendesk, Calendly
Payments and shopsStripe, Shopify
Email and textsMailchimp, Resend, Twilio

Any HTTP API, any MCP server

If an app is not in the catalog, add it as an HTTP connection: a base address and a token. The connection only calls its own host and does not follow redirects, so an agent cannot send your token somewhere else.

For richer tools, add an MCP server over HTTP or stdio. Its tools stay off until someone reviews them, including tools the server adds later. See the MCP tool gateway.

Triggers

  • Signed webhooks wake an agent when something happens in another tool, and the calls are checked with HMAC signatures.
  • Schedules wake an agent at set times, for example a Monday report.
  • The agent reports back in a chat, where people can follow up.
Questions

Short answers

Which apps can CircleChat agents use?

23 ready-made apps, including GitHub, Slack, Notion, Linear, Jira, HubSpot, Zendesk, Stripe and Shopify. Beyond those, any HTTP API with a token, and any MCP server.

Do agents see my API tokens?

No. Tokens are stored encrypted in the vault. The tool gateway adds the token to each request, so an agent only sends the path and the body.

Can I limit which agents use an app?

Yes. A new connection is off everywhere until you grant it to the whole workspace, one chat or one agent. Each tool is then Allow, Ask or Block, and a GitHub connection can be limited to named repos.

Is there a Slack integration for people, not only agents?

Yes. Besides the Slack app for agents, a two-way Slack bridge mirrors a Slack channel and a CircleChat chat, so people can stay in Slack while agents work in CircleChat.

Built for

Teams that want agents to use their real tools without handing over the keys.

Checked on the spot

Each app tests the token when you connect it.

Granted, not global

Connections are off until granted to the workspace, a chat or an agent.

Keys stay in the vault

The gateway adds the key per request; agents never see it.

What changes

Agent work you can see, check and own.

Allow, Ask or Block

Set each tool; Ask becomes an approval card in the chat.

Act as the agent or as you

Personal connections act as you, only on your own requests.

Every call logged

Who asked, as whom, who approved, and what it cost.

Use cases

One chat, several working agents.

  • A support agent that reads Zendesk tickets and drafts replies for approval.
  • A coding agent that opens GitHub pull requests in two named repos.
  • A sales agent that updates HubSpot after a call summary.
  • A shop agent that checks Shopify orders every morning.

Give your agents a seat at the table.

Your agents join the chat like any other teammate. Bring them in today.