Turn Slack into MCP tools
Give your AI agent Slack tools. Writ turns your Slack workflows into authenticated MCP tools your agent can call, taking real actions on your own account.
{
"mcpServers": {
"writ-slack": {
"url": "https://api.usewrit.app/mcp/your-workspace",
"headers": { "Authorization": "Bearer wt_8f2c...a91" }
}
}
} No Slack MCP server yet? Build one in minutes
Record the Slack task once, or describe it to an AI session, and Writ turns it into an MCP tool your agent can call, taking real actions on your own Slack account.
- 1Record a Slack action once
Open the recorder and open admin analytics on Slack in a real browser. Writ captures the steps, login and 2FA included, into a workflow.
- 2Publish it as an MCP tool
One click exposes the workflow as an MCP tool with a typed input schema, alongside a REST endpoint. Your agent picks it by its description.
- 3Call it from any MCP client
Point Claude Desktop, Claude Code, Cursor, or any MCP client at your Writ server. The Slack tool acts on your own account and returns structured output.
Browse supported MCP clients, see what's possible on workflows, or search for another site. Free to start. See pricing.
Slack has no MCP server
Read-only website-to-MCP tools can summarize a Slack page, but they can't do anything on it. Writ turns the Slack workflows you build into MCP tools your agent calls to take real actions (search, extract, submit), authenticated, on your own Slack account.
Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
Slack tools your agent can call
Each tool is a real Slack workflow with a typed input schema and structured output. Your agent picks the right one by its description.
slack.export_membersExport the workspace member directory.Example tool schema
{
"name": "slack.export_members",
"description": "Export the workspace member directory.",
"input_schema": {
"type": "object",
"properties": {
"query": { "type": "string", "description": "What to look up on Slack." }
},
"required": ["query"]
}
} Add the server to any MCP client
Copy the config into your client and authenticate with a wt_ key. Tools appear automatically.
{
"mcpServers": {
"writ-slack": {
"url": "https://api.usewrit.app/mcp/your-workspace",
"headers": { "Authorization": "Bearer wt_8f2c...a91" }
}
}
} {
"mcpServers": {
"writ-slack": {
"url": "https://api.usewrit.app/mcp/your-workspace",
"headers": { "Authorization": "Bearer csk_3a90...f4d" }
}
}
} Per-client setup. Step-by-step config for each client lives on the per-client pages: Claude Desktop, Claude Code, Cursor, Windsurf.
Your agent acts on your own Slack account
Writ signs into your own Slack workspace through a Persona, including SSO, and runs inside that authenticated session for UI-only actions.
Use Writ on your own Slack workspace. Authorized automation of your own account.
Other ways to work with Slack
Slack MCP questions
Is there an official Slack MCP server?
Are there ready-made Slack MCP tools I can install?
How is this different from a read-only website-to-MCP tool?
Does it work with Slack login and 2FA?
Which MCP clients can use these Slack tools?
Is it allowed to use Slack this way?
Give your agent Slack tools
Build a workflow, publish it as an MCP tool, and call it from any MCP client. Get started free.