# Catch up on Slack. Get back to work.

Source: https://corespeed.io/integrations/slack

Connect Slack to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent searches the channels your account can see, reads a thread, and hands back the decisions, the open questions and a next-step plan. It signs in with your own Slack account, never reads past your workspace permissions, and posting is a separate call.

## Set up an agent

Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`

It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Slack after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up

## A good discussion. A clear next step

Have your agent turn a thread into a recap and a proposed plan. Unresolved decisions stay visible instead of guessed.

You ask your agent: "Read the launch discussion in Slack. Summarize the decisions and draft a next-step plan. Flag anything the team has not agreed yet."

It calls CoreSpeed:

- `slack__search_messages`: ok, 388 ms
- `slack__conversations_replies`: ok, 452 ms

It reads from: Slack.

### Discussion recap: Here is where we landed.

Start with the customer use case. The launch date and the first test’s success measure still need a decision.

**Suggested next steps**

- Draft focused messaging.
- Prepare a landing page around the chosen use case.

**Do not assume**

- A launch date has not been agreed.
- The team has not picked a success measure.

_Illustrative discussion · Nothing posted to Slack_

All connectors: https://corespeed.io/docs/connectors

## Keep the decisions. Skip the scroll

Requests you can make once Slack is connected. The data is fictional.

### Catch up on a discussion

#launch · the short version · Conversation summary

- Agreed: Lead with the customer use case
- Still open: Confirm the first test’s scope
- A focused recap

### Recover a decision

What did we decide? · Context for your next task

- Decision: Start with one clear use case
- Reason: Make the first result easy to see
- The reasoning stays with the answer

### Turn discussion into a plan

A launch plan · Slack + Linear

- Next step: Draft the page and messaging
- Before launch: Agree on the success measure
- Suggested work · No tasks created

Full example: https://corespeed.io/integrations/slack-linear (Markdown: https://corespeed.io/integrations/slack-linear.md)

## Keep your agent. Bring your work

One CoreSpeed account, across compatible agents.

1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in.
2. **Connect Slack**: Authorize the account and the content you need.
3. **Start with one task**: Ask for a summary, a brief, or a draft. Review the answer.

Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor

## Questions

### Is this a bot I chat with inside Slack?

No. It brings Slack tools into an agent such as Claude Code, Codex, or Cursor. It is not a hosted Slack chatbot.

### Can it read every private channel?

No. It sees only what the connected Slack account can see, within the scopes you grant. CoreSpeed does not bypass workspace permissions.

### Do I have to switch agents?

No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once.

### Can my agent access every account in our organization?

No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private.

### Does this work without connecting an account?

No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors

Every tool and price: https://corespeed.io/catalog/slack

## Related pages

- [Approval gates for AI agent tool actions](https://corespeed.io/solutions/agent-approvals): Set approval policies for writes through CoreSpeed. Review held tool actions while your team keeps using its preferred agents.
- [Discord for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/discord): Give your agent your Discord profile, your servers, and your member profile in each. Read only: no channels, no messages.
- [Project update with GitHub and Slack](https://corespeed.io/integrations/github-slack): Bring GitHub changes and Slack project discussions into one update your team can act on.
- [Microsoft Teams for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/microsoft-teams): Catch up on your Teams chats and prepare the channel update inside the agent you already use.
- [Pushbullet for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/pushbullet): Let your agent push a note, a link or a file to your phone when a task finishes, from the agent you already use.
- [Discussion to plan with Slack and Linear](https://corespeed.io/integrations/slack-linear): Turn a Slack discussion into a proposed plan, grounded in the issues your team already tracks in Linear.
- [Discussion to plan with Slack and Notion](https://corespeed.io/integrations/slack-notion): Turn a Slack discussion into a proposed plan, grounded in the goals and constraints recorded in Notion.
- [Webex for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/webex): Catch up on Webex spaces, find the right person, and set up the follow-up meeting from the agent you already use.
- [WhatsApp Business for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/whatsapp): Check WhatsApp Business templates, read delivery status, and send customer messages from the agent you already use.

## Sources

- Connectors: https://corespeed.io/docs/connectors

Reviewed 2026-11-07.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)
