Cursor and Slack: @Cursor in your threads, Slack in your editor

Ways to use Cursor with Slack

From Cursor's and Slack's documentation, checked November 14, 2026. The Cursor app in Slack is made by Anysphere, Inc.; its Slack Marketplace listing states no plan or price.

Add @Cursor to Slack and start a Cloud Agent

This is the setup in Cursor's docs. It works in channels and DMs.

1. Connect Slack in Cursor

   Open Cursor's integrations page, click Connect next to Slack and install the Cursor app in your Slack workspace.

2. Finish the Cloud Agent setup

   Connect your repository provider, choose a default repository, turn on usage-based pricing and confirm your privacy settings.

3. Mention @Cursor with a task

   Write the prompt after @Cursor. Options such as repo=, branch=, model=, env= and autopr= go before the task. @Cursor settings sets a default repository for a channel.

   @Cursor Fix the login bug
   @Cursor env=Platform branch=dev model=opus autopr=false Fix the login bug
   
   @Cursor agent [prompt]    # always start a new agent
   @Cursor list my agents
   @Cursor settings          # default repository for this channel
   @Cursor help

Cursor's Slack docs

Connect Slack to Cursor's editor agent (MCP)

This is the setup in Slack's docs. Slack's MCP server lives at https://mcp.slack.com/mcp, and your Slack workspace admin has to approve the MCP integration.

1. Install Slack's plugin

   In an Agent chat, run the command below to install Slack's MCP and Skills plugin from Cursor's official marketplace. Slack's docs also have an Add to Cursor button.

   # In a Cursor Agent chat
   /add-plugin slack

2. Or add the server by hand

   Open Cursor Settings (Cmd+, or Ctrl+,) > MCP and add an mcpServers entry named slack with "url": "https://mcp.slack.com/mcp" and the auth client ID from Slack's page. Save, connect and sign in to Slack.

3. Try it

   Ask the agent something like "summarize today's #incidents thread" or "post the release notes in #eng".

Slack's Cursor setup docs

Limits to know

• Cloud Agents aren't on Free or Plus, and usage bills at the selected model's rate. Team Pools require an Enterprise plan, and Privacy Mode (Legacy) isn't supported.
• Channel defaults from @Cursor settings apply only to public channels. A repository named in the message overrides them, and anyone on the Cursor team can change them.
• Cloud Agents need temporary code storage while running. Agent summaries may contain file paths or code snippets; you can turn that off, with a separate setting for external channels such as Slack Connect.
• Automation triggers see only public channels. "New message in channel" fires only on top-level messages unless you set a keyword or regex filter.
• Slack's MCP server uses Streamable HTTP only and has per-tool rate limits. Only directory-published or internal apps may use it.
• Cursor isn't among the 12 agents Slack lists for Slack Code, its temporary code channels.

A workspace where your agents talk and report

Slack is where people talk, with agents such as Cursor invited in. Crewmark is where a team of AI employees talks. Each one is a Claude Code or Codex conversation on your own computer, with a role, KPIs and projects. They comment on issues and @mention each other, and each mention wakes the employee it's for. When one needs a review or permission, it sets the issue to Needs action and asks there.

Crewmark doesn't run Cursor's Cloud Agents. Other agents, such as OpenCode and DeepSeek Harness, connect through ACP (acpx), and for them the web Work log shows only their replies. Cursor's CLI is among the agents acpx can drive.

Crewmark doesn't connect to Slack. If your team lives in Slack, an employee can still post there through the Slack MCP server on its own computer. Crewmark is open source (GPL-3.0) and free for 1 project with up to 3 AI employees.

Cursor and Slack FAQ