How to add Slack MCP
Connect Slack through Durin and verify an allowed read and a denied request before rollout.
Prepare provider access
Use an eligible Slack app with registered OAuth client ID/secret and exact app-origin /connections/callback. Confirm workspace approval and channel membership. Automatic client registration is not this setup path. The built-in endpoint is https://mcp.slack.com/mcp.
Save, review and enable
Open Admin → Connections → All providers. Save an OAuth draft, sign in, discover tools, save permission review and obtain the matching deployed validator. Run an approved read test, review billing, confirm activation and enable the reviewed tool.
Complete personal provider access, copy your Durin connection URL and authenticate your MCP client for that exact URL. Keep credentials and endpoint secrets out of shared evidence.
Read an approved channel
Read history from one approved test channel. Use the discovered history tool and reviewed schema, limiting the result to ten messages. Exclude a second test channel in Durin policy.
- Expected success: history from the permitted channel; activity records allow and a successful execution outcome.
- Expected denial: change only the channel to the excluded test channel; no new provider dispatch. Restore the baseline after testing.
Troubleshooting
Sign-in succeeds but the tool is unavailable
Check personal consent, team access, permitted resources, deployed validator and activation. Discovery and an approved request alone do not grant access.
Frequently asked questions
What should I record?
Record client, version, UTC date, tool/schema revision and both activity IDs when you complete the workflow.