Skip to content

IM

Slack MCP connector

The Slack connector lets Claude, ChatGPT, Cursor and other MCP clients read channels and threads, post and edit messages, search conversations, share files and look up people in Slack, with each person acting under their own Slack access.

Connect on Elaichi How to connect

  • How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Slack to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Slack once

  1. Open Connections, choose Add connection, and pick Slack.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Supply your own Slack app, then approve. Slack needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

slack
Slack
1Password
360learning
7shifts
Acquire
Ada
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Slack to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Slack to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Slack to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Slack to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Connect Slack on Elaichi See pricing

Use cases

What teams do with Slack through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Support

    Catch up on an escalation thread

    Ask for the full reply chain in a customer escalation channel and get a plain summary of what was promised, by whom, and what is still open before you answer the customer.

  • Sales

    Post the call recap to the deal channel

    Dictate the notes from a discovery call and have them posted to the account's Slack channel as a tidy message, then fix a wrong figure by editing the message rather than reposting.

  • Operations

    Find where a decision was made

    Search Slack for the conversation where the team agreed on the new vendor, pull the relevant messages, and share the answer with someone who was not in the channel.

  • People

    Reach a teammate from an email address

    Look up a new hire by the address in the HR system, confirm their Slack profile, and open a direct message to send them their first week schedule.

  • IT

    Review who signed in and from where

    Pull the workspace access logs for the last week, list sign-ins from unfamiliar locations, and drop the summary and a supporting file into the security channel.

  • Finance

    Check who is on a paid seat

    List the workspace's billable members against the current headcount so the monthly Slack invoice can be reconciled without asking an admin to export anything.

Try asking

  • “Summarize the last 50 messages in #support-escalations.”
  • “Which channels did the design team join this month?”
  • “Post the release note to #product-announcements.”

See all 23 Slack tools below

AI tools

Slack tools for your AI agents

23 tools are ready to call through Elaichi's MCP endpoint the moment you connect Slack, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Slack gets you

6 screens from the product, each doing one job for your Slack account.

The agent

Ask about channels, get answers from Slack.

Plain language questions return live messages, channels and users from Slack.

  • messages
  • channels
  • conversations
  • users

Ask Elaichi to work across your apps.

Summarize the last 50 messages in #support-escalations.

Which channels did the design team join this month?

Post the release note to #product-announcements.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Slack here.

One governed MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

 • Connected 4 minutes ago
Cursor
S

Sofia Ricci

 • Connected 2 hours ago
ChatGPT
C

Clara Nowak

 • Connected Yesterday

Tool catalog

23 Slack tools ready without custom code.

Browse conversations, replies, users and access log methods in one catalog.

  • List all Slack users
  • Get single Slack user by ID
  • List all Slack team billable info
  • Get single Slack team billable info by ID
ElaichiTools
Tool Action Description
List all Slack users List Get a list of all users in the Slack workspace. Returns user objects including id, team_id, name, deleted status, real_name, timezone info, profile with email and images, admin and bot flags.
Get single Slack user by ID Get Get information about a specific user in Slack by user id. Returns user fields including id, team_id, name, real_name, timezone info, profile details (avatar, status, email, images), and admin/owner flags.
List all Slack team billable info List Get billable users information for the current team in Slack. Returns billing_active status for each user indicating billing eligibility per Slack's Fair Billing policy.
Get single Slack team billable info by ID Get Get billable users information for the current team in Slack. Returns billing_active status per user indicating eligibility for billing under Slack's Fair Billing policy.
List all Slack team access logs List Get access logs for the current team in Slack. Returns user_id, username, date_first, date_last, count, ip, user_agent, isp, country, and region for each access log entry.

Toolboxes

Every team gets its own Slack toolbox.

Curate one toolbox per team and scope it to that team alone.

  • Support
  • Engineering
  • Sales
  • People Ops
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Slack · escalation channels and replies

 Slack starter 18 Mar 4, 2026

Engineering toolbox

Slack · incident channels and threads

 — 9 Mar 2, 2026

Sales toolbox

Slack · deal rooms and customer channels

 — 24 Feb 27, 2026

People Ops toolbox

Slack · users and access logs

 Slack starter 6 Feb 19, 2026

Marketing toolbox

Slack · announcement channels and messages

 — 31 Jan 30, 2026

IT Admin toolbox

Slack · billable info and access logs

 — 12 Jan 22, 2026

Shared connections

Teammates post to Slack without a token.

See who connected each Slack account and which teams and members share it.

  • Support
  • Sales EMEA
  • Engineering
  • Marketing
ElaichiConnections
Connection Scope Status Access
SL

Slack (Support)

Connected by Emma Laurent

 Personal • Active 1 team · 6 members
SL

Slack (Sales EMEA)

Connected by James Whitfield

 Organization • Active 3 teams · 24 members
SL

Slack (Engineering)

Connected by Sofia Ricci

 Organization • Active 2 teams · 11 members
SL

Slack (Marketing)

Connected by Daniel Ortega

 Personal • Needs re-auth 1 team · 3 members
SL

Slack (People Ops)

Connected by Clara Nowak

 Personal • Active Not shared
SL

Slack (IT Admin)

Connected by Michael Brennan

 Personal • Active 2 teams · 9 members

Audit log

Every Slack call is on the record.

When, who, what happened, type and resource for each message and channel.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM
E

Emma Laurent

[email protected]

 Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM
J

James Whitfield

[email protected]

 Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM
S

Sofia Ricci

[email protected]

 Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM
D

Daniel Ortega

[email protected]

 Slack Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
C

Clara Nowak

[email protected]

 Slack Messages Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
M

Michael Brennan

[email protected]

 Slack Messages List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule turns channel history into a digest.

Six steps fetch conversations, group them, draft a digest, await approval, post to Slack.

Slack digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. ✓

    Schedule

    Every weekday at 08:00

    0.2s
  2. ✓

    Fetch messages

    Slack

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s

  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve

  6. Post the digest

    Slack

    Queued

Collections and dashboards

Slack activity numbers arrive before anyone asks.

Four metrics, 14 days of messages created and a team breakdown, refreshed on schedule.

Slack health

Refreshed 4 minutes ago · every 15 minutes · from the messages collection

Live

Messages

1,284 ↓ 12%

Channels

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Messages created

Last 14 days

By team

Share of activity

Support 34%

Sales EMEA 27%

Engineering 21%

Marketing 18%

Related connectors

More from the catalog

Browse all 400+ connectors →

FAQ

Frequently asked questions

How do I connect Slack to Claude?

First connect Slack inside Elaichi, then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Slack requires an OAuth application registered in your own Slack workspace, so an admin brings a client ID and secret once, and after that everyone signs in with the normal Slack authorization screen. Once that is done, each person approves Slack for themselves and no one else touches a credential.

Does Slack work with ChatGPT and Cursor as well as Claude?

Yes. Slack is connected once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. There is nothing separate to set up for each client.

What can an AI agent actually do with my Slack data?

Through Elaichi, an agent can read the history and replies in Slack channels you belong to, search across your Slack messages, post new messages, edit or delete ones it posted, join channels and open direct messages. It can also look up people by name or email, list and upload files, and for admins, read workspace access logs and billing information. In everyday terms, it can summarize a thread, draft and post an update, find who said what, and share a file.

Does connecting Slack give the AI access to every channel in my workspace?

No. Every request to Slack runs as the person who signed in, so the agent sees only the channels, direct messages and files that person can already see in Slack. Elaichi can narrow that further by hiding actions or restricting a team, but it can never grant access to a private Slack channel the person was not already in.

Can my team share one Slack connection?

Yes. One person registers the Slack application and connects it in Elaichi, then shares the connection with a team, so nobody else ever handles the client ID or secret. Each teammate still signs into Slack as themselves, so their messages post under their own name and the audit log records exactly who did what.

Can I stop an agent from deleting or changing messages in Slack?

Yes. In Elaichi, restrictions on the Slack connector are set per action, so you can allow reading channels and posting messages while blocking editing, deleting, or uploading files. A blocked action is never shown to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.

What happens to a Slack connection when someone leaves the company?

When a person is offboarded in Elaichi, their access to Slack through every connected client ends immediately. A Slack connection shared with a team keeps working for everyone else, and if the company wants to remove Slack entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

Put Slack in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.

Connect Slack Talk to us