Skip to content

Connect Cursor to Slack

Connect Cursor to Slack in 3 steps: 1. Sign in to ApexGenius and connect Slack. 2. Add the ApexGenius MCP server. 3. Start using Slack in Cursor.

1,000 free credits · No card required

How to connect Slack to Cursor

  1. 1Sign in to ApexGenius and connect Slack
  2. 2Add the ApexGenius MCP server to Cursor
  3. 3Start using Slack in Cursor
  1. 1Slack

    Connect Slack to ApexGenius

    Connect Slack

    Slack opens its own sign-in. Sign in and allow ApexGenius.

  2. 2ApexGenius

    Connect ApexGenius to Cursor

    Choose Cursor

    Back on Start, pick Cursor and copy the prompt.

  3. 3ApexGenius

     

    Approve access

    ApexGenius opens its approval page. Review the access, then approve.

Add the ApexGenius MCP server to Cursor

Cursor reads MCP servers from ~/.cursor/mcp.json for every project, or from .cursor/mcp.json inside one project. The Customize page manages the same servers.

  1. Add the apexgenius entry to mcpServers. Keep any servers already there.
  2. Open Customize in Cursor, find apexgenius and choose Connect.
  3. Approve ApexGenius in your browser.
Add to ~/.cursor/mcp.json
{
  "mcpServers": {
    "apexgenius": {
      "url": "https://server.autom8.pro/mcp"
    }
  }
}

Check it. Cursor lists a connected server’s tools under Available Tools. By default it asks for your approval before it runs one.

Steps follow Cursor documentation, Model Context Protocol (MCP) (opens in a new tab), read November 12, 2026.

Then ask Cursor

Show my connected Slack accounts. For the account I choose, discover the read-only channel-list tool and list up to five channel names. Do not read or send messages.

Start free
Written setup, step by stepShow

Before you start

  • A Slack account in each workspace and permission to authorize the app. Workspace admins may need to approve it.

1. Connect Slack to ApexGenius

  1. Open Slack in Connections. Sign in to ApexGenius, open Connections, and choose Slack.
  2. Choose the Slack user and workspace. Sign in with the intended Slack account. Check the workspace and requested access before you allow it.
    Slack's page titled Allow the ApexGenius app to access Slack, with a workspace picker on the left, the list of permissions on the right, and Cancel and Allow buttons.
    Connect opens Slack's own permission page. Pick the workspace, review what ApexGenius can view and do as you, then choose Allow.Open full-size image (opens in a new tab)
  3. Add your other accounts. Check the saved workspace and user. Choose Add connection and repeat for each account. Use a clear name for each connection. Reconnect signs in to the same user and workspace.
  4. Choose tools and AI access. Open Tools and Access for each connection. Start with Read only for your AI. Enable writes only when you need them. Enabled writes run when called.
  5. Try one read per account. Name the intended Slack connection in your request. Check that the result and Tool Activity show that account.
Connect Slack →

2. Connect ApexGenius to Cursor

Use this server address when adding the connection:

https://server.autom8.pro/mcp

The steps are above, under Add the ApexGenius MCP server to Cursor. These notes apply to Cursor only.

  • No client ID or secret. Cursor signs in with OAuth and registers itself with ApexGenius, so mcp.json needs only the address.
  • Enterprise teams. An MCP allowlist can limit which server addresses run. If apexgenius does not connect on a team account, ask your Cursor admin to allow the ApexGenius address.
  • Turning it off. Enable or disable the server from Customize in the sidebar.
  • Access. When ApexGenius asks what Cursor may use, choose Read only for the first test, or Custom to limit it to the tools you need.

3. Verify one safe read

Show my connected Slack accounts. For the account I choose, discover the read-only channel-list tool and list up to five channel names. Do not read or send messages.

Show my connected Slack accounts. For the account I choose, discover the read-only channel-list tool and list up to five channel names. Do not read or send messages.

Compare the selected workspace and user with Slack. Repeat for each connection. A successful read does not verify writes or access to another account.

Full guide: the Slack setup guide.

What it looks like in Cursor

Illustration of a task, not a recorded customer result. Your answers come from the account and dates you choose.

How the route works
Cursor
CursorApexGenius MCP route
Show my connected Slack accounts. For the account I choose, discover the read-only channel-list tool and list up to five channel names. Do not read or send messages.
ApexGenius
Working with ApexGenius3 reads
RequestConnected read
Account scopeAuthorized connections checked
Salesforceapex_call_read_toolsalesforce_read · Find matching recordsComplete
Salesforceapex_call_read_toolsalesforce_read · Read related activityComplete
n8napex_call_read_tooln8n_get_workflow · Check workflow statusComplete
Cursor

Three safe example reads returned results. Nothing was changed.

Read-only route
Cursor

Try asking

Show my connected Slack accounts. For the account I choose, discover the read-only channel-list tool and list up to five channel names. Do not read or send messages.

In my chosen Slack account, find the thread I name and summarize its decisions.

Draft a reply for this Slack thread. Show the account, recipient and text before sending.

What Cursor can do in Slack

3 operations: 2 read, 1 write. Read looks things up and changes nothing. Writes change Slack and run only when you turn them on.

Slack gateway tools

2 read · 1 write
  • slack_search_toolsread
  • slack_call_read_toolread
  • slack_call_toolwrite

You choose the access. When you approve Cursor, pick Full access, Read only, or Custom.

Each connection identifies both the Slack user and workspace. Two users in one workspace remain separate.

Private channels and DMs follow the connected user’s Slack access. ApexGenius does not add access to other users’ private conversations.

The read route refuses writes and anything not classified as a read. Enabled writes run when called.

ApexGenius uses Slack's official tools and Slack's Web API. Admin methods need a Slack org admin on Enterprise Grid. Sign-in, token and app-management methods are not available.

Disconnecting stops future calls. It does not undo a sent message or another completed change.

Start free

Questions about connecting Cursor to Slack

Updated November 12, 2026.

How do I connect Cursor to Slack?

Connect Cursor to Slack through ApexGenius in three steps. Sign in to ApexGenius and connect Slack with Slack OAuth for your user and workspace. In Cursor, add an apexgenius entry with the ApexGenius MCP address to mcpServers in ~/.cursor/mcp.json, then choose Connect on the Customize page. Then open a task in Cursor and ask a question about your Slack. Start with a read, so nothing changes.

How do I check that Cursor can use Slack?

Open Customize in Cursor and find apexgenius among the MCP servers. Its tools should appear under Available Tools. If it is listed but not connected, choose Connect and finish the browser sign-in. On an Enterprise team, the MCP allowlist may need the ApexGenius address. Then ask: “Show my connected Slack accounts. For the account I choose, discover the read-only channel-list tool and list up to five channel names. Do not read or send messages.”

Is there a Slack MCP server for Cursor?

Yes. ApexGenius is an MCP server that Cursor connects to once. It carries your Slack connection and 3 Slack operations, so Cursor does not need a separate Slack integration or plugin. You set it up one time and add each agent the same way.

What can Cursor do in Slack once it is connected?

Cursor can use 3 Slack operations through ApexGenius: 2 that find what Slack can do and run a classified read on the account you pick, and 1 that runs a write you have enabled. Together they reach Slack’s official tools and Web API, within your Slack permissions.

Can Cursor read my private Slack channels and DMs?

Only what the connected Slack user can already see. Private channels and DMs follow that user’s Slack access, and ApexGenius adds none for other people. Each connection is one Slack user in one workspace, and the read tool must be enabled before Cursor can use it.

Can Cursor change my Slack?

Not until you enable writes. Start with Read only, and the read route refuses writes. Turn writes on only when you need them. Enabled writes run when called, and disconnecting does not undo a sent message. Admin, sign-in and token methods are not available.

Can I use the same Slack connection with Claude, ChatGPT, Grok Bot or Muse?

Yes. One Slack connection in ApexGenius works with every compatible agent you add, including Claude, ChatGPT, Grok Bot or Muse. Each agent gets its own access choice and its own short setup, so you can pick read only for one agent and more for another.

Connect Slack to Cursor today

Start free

1,000 free credits. No card required. Disconnect any time.