← All integrations

Slack Bot MCP server

87 operations10 webhooks

Slack workspace access with a bot token for messages, conversations, files, users, user groups, reminders, calls, canvases, and team info, plus Events API webhooks.

Use Slack Bot in Claude, ChatGPT, Cursor or another MCP client

Connect Slack Bot once in Corsair, then add one MCP address to your agent.

Connect Slack Bot
Setup steps for Claude, ChatGPT, Cursor and Claude Code

Building your own app on the Corsair SDK? Get API keys

Try Slack Bot with your agent

Connect Slack Bot, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Slack Bot on my account, then run one read-only example and show me the result.

Runs once, when you ask

Slack Bot tools and triggers

Tools are what your agent can do in Slack Bot through Corsair's MCP server. Triggers are the Slack Bot events a routine can start from.

Conversations

  • ArchiveDestructive

    Archive a conversation

    conversations.archive

  • CloseWrite

    Close a direct message or group conversation

    conversations.close

  • CreateWrite

    Create a public or private channel

    conversations.create

  • FindRead-only

    Search conversations by name

    conversations.find

  • InfoRead-only

    Retrieve information about a conversation

    conversations.info

  • InviteWrite

    Invite users to a channel

    conversations.invite

  • JoinWrite

    Join a public channel

    conversations.join

  • KickDestructive

    Remove a user from a conversation

    conversations.kick

  • LeaveWrite

    Leave a conversation

    conversations.leave

  • ListRead-only

    List conversations in the workspace

    conversations.list

  • List For UserRead-only

    List the conversations a user belongs to

    conversations.listForUser

  • MarkWrite

    Move a conversation read cursor

    conversations.mark

Connect Slack Bot to Claude, ChatGPT or Cursor

  1. 1

    Connect Slack Bot in Corsair

    Sign in to Slack Bot once in Corsair. Corsair stores the credential encrypted and makes the Slack Bot API calls for your agent, so it never goes into a prompt or a config file. Connect Slack Bot

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Slack Bot. On a ChatGPT personal plan, connect Slack Bot here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Slack Bot's read and write operations run right away and its 11 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/slackbot, add the Slack Bot plugin, and connect with OAuth. Then call methods like corsair.slackbot.api.calls.add() from your app. Corsair verifies webhooks, stores tokens, and syncs data per tenant.

Yes. Slack Bot needs an OAuth app with scopes that match what you automate. Register the app in Slack Bot, configure redirect URLs, then connect through Corsair or managed OAuth in Hub.

Yes. One Corsair client can hit Slack Bot, GitHub, Notion, Stripe, and the rest. Trigger Slack Bot from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for slack workspace access with a bot token for messages, conversations, files, users, user groups, reminders, calls, canvases, and team info, plus events api webhooks. Common builds include sync jobs, admin tooling, and agents that call Slack Bot APIs from your backend. Webhook handlers react to Slack Bot events and fan out to Slack, email, or other plugins in the same tenant. Local DB entities let you query synced Slack Bot records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Slack Bot API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/slackbot in the open repo. When Slack Bot ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Slack Bot data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Slack Bot data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Slack Bot on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 11 destructive Slack Bot operations. You can change a link's mode at hub.corsair.dev/me.