Kiwi for Slack
Have the agent on a Kiwi step read the Slack thread behind its task and reply there with its result, through Slack's MCP server.
- Your agent works in Slack through its own connection. Kiwi does not call Slack and never holds its credentials.
- A workflow skill can list Slack among the tools it requires. When you supply your agent's available tools to a skill check and Slack is not among them, the check reports
SK15-UNSUPPORTED-TOOL. - A project Admin can add links to Slack, with notes, under Connections and bind them to the steps that use them. The agent reads them with
list_connections. - The agent can report the tools and plugins it ran with, including its Slack connection, with
report_configuration. - The agent submits links to its work in Slack as the step's outputs. People review them, and sign-off stays with the people your workflow names.
What your agent can do in Slack
- Search messages, files, channels and users to find the discussion behind a request.
- Read a channel's full history or a whole thread, and send, schedule or draft a message.
- Create, update or read a canvas, such as a checklist the team keeps for a release.
- React to a message to acknowledge it, or upload a file and share it to a channel.
- Connect from a client that Slack lists, such as Claude Code or Cursor, or from your own Slack app if it is in the Slack Marketplace or internal to the workspace, because unlisted apps cannot use MCP.
Set up
Connect your agent to Kiwi
Add Kiwi's hosted MCP server,
https://kiwiflow.io/mcp, to your coding agent.Connect your agent to Slack
Add the Slack MCP server to your agent with this URL. The credentials stay with your agent.
https://mcp.slack.com/mcpExample skill
Publish instructions like these as a workflow skill that lists Slack among its required tools.
Read the Slack channel and thread link from the assignment inputs. Read the whole thread to collect the request and decisions already made. Reply in the thread with the result and the pull request link. Submit the channel ID and the reply's timestamp as the step's outputs. New requests raised in the thread go to the channel owner named in the inputs. If a workspace admin has not approved the app, call report_blocker.