Slack MCP Integration

Weldable's Slack MCP integration gives your AI agents full read and write access to your workspace through 22 actions. Slack launched its own MCP server in February 2026 and it's now generally available, with over 50 partners building on the protocol. Weldable builds on this momentum by handling OAuth, token refresh, and multi-integration chaining so you can go from connected to automated in minutes.

Where Slack's official server focuses on search and retrieval, Weldable covers the entire surface: posting messages, scheduling sends, managing channels, reacting to conversations, and looking up users. Your agent works in plain English. Tell it what you need and it maps your intent to the right API call.

Use cases

Automated standup summaries

Your agent uses read messages with the oldest parameter to pull the last 24 hours from #engineering. It extracts key updates, formats them into a digest, and calls send message to post the summary to #standup-notes. Pair this with Google Calendar to include who's out of office that day, giving the team a complete morning briefing without anyone writing a single status update.

Incident response coordination

When a monitoring alert fires, your agent calls send message to post the alert details to #incidents with structured formatting. As the investigation unfolds, it uses reply to thread to keep all updates in one place. Team members can add reaction with a eyes emoji to claim ownership, and your agent tracks these reactions to know who's on point. If the incident needs a dedicated space, it calls create channel and invite to channel to spin up a war room.

New hire onboarding automation

Your agent watches for new members joining #general. It calls create channel for the onboarding cohort, invite to channel to add their manager and buddy, set channel topic with key dates and links, and send message with a structured welcome post. The entire process runs without anyone remembering to do each step manually.

Cross-tool reporting

Pull data from Google Sheets, summarize it with Anthropic's Claude integration, and have your agent call schedule message to deliver the report to #metrics at 9am every Monday in your team's timezone. The schedule message action accepts Unix timestamps, so your agent handles the timezone math and queues the delivery.

Channel lifecycle management

Your agent calls list channels to audit the workspace, then get channel info to check activity levels for each one. Channels with no posts in 30 days get a check-in message via send message. If there's no response after a week, your agent calls archive channel to clean up. This keeps the workspace organized without anyone manually triaging dead channels.

How it works

Connect your Slack workspace through a one-click OAuth flow. Weldable requests only the scopes your agent needs: chat:write for posting, channels:read and channels:history for reading, reactions:write for reactions, and users:read for lookups. Tokens refresh automatically in the background.

Once connected, describe what you want in natural language. Weldable matches your intent to the right action, resolves channel names to IDs, formats your content in Slack's mrkdwn syntax, and executes the API call. Your agent can chain multiple actions together: read from one channel, process the content, and post results to another.

Tips

Slack uses mrkdwn, not Markdown. Bold is *text*, italic is _text_, and user mentions use <@U12345> format. Your agent handles this formatting, but knowing the syntax helps when you want precise control over message appearance.

Scope your reads with time parameters. The read messages action supports oldest and latest parameters as Unix timestamps. Use these to fetch only the messages you need instead of pulling entire channel histories. This matters because Slack tightened rate limits on conversations.history in May 2025 for non-Marketplace apps.

Thread replies keep channels clean. When your agent follows up on a message, use reply to thread instead of posting a new top-level message. This keeps discussions organized and prevents important updates from getting buried in channel noise.

Reactions work as lightweight workflow signals. Your agent can call add reaction to mark messages as processed, acknowledged, or flagged. A checkmark reaction on a support request signals "handled" without adding a reply. This pattern is especially useful in high-volume channels.

Channel names resolve automatically. You can reference #engineering in your commands and Weldable converts it to the correct channel ID behind the scenes. No need to look up C01ABC123 manually.