Slack provides an official remote MCP server atDocumentation Index
Fetch the complete documentation index at: https://www.truefoundry.com/llms.txt
Use this file to discover all available pages before exploring further.
https://mcp.slack.com/mcp. You can connect it to the TrueFoundry MCP Gateway so users can search Slack, read channels and threads, send messages, and work with canvases through approved AI clients.
Prerequisites
- A TrueFoundry account with permission to add MCP servers.
- A Slack workspace where you can create and install apps.
- Your TrueFoundry control plane base URL.
The examples below use Slack OAuth scopes that expose every currently supported Slack MCP capability. Remove scopes your workspace does not need before creating the app.
Create a Slack App
Open the Slack app dashboard
Go to api.slack.com/apps. Select an existing app if you want to reuse one, or choose Create New App.
Create the app from a manifest
Select From an app manifest, choose the target workspace, switch the manifest editor to JSON, and paste the following manifest.Replace
<tfy-control-plane-base-url> with your TrueFoundry control plane URL.Slack Scope Reference
Use the table below to trim the manifest before you create the app.| Capability | Slack scopes |
|---|---|
| Search public and private messages | search:read.public, search:read.private, search:read.mpim, search:read.im |
| Search files | search:read.files |
| Search users | search:read.users |
| Send messages | chat:write |
| Read channels, groups, DMs, and threads | channels:history, groups:history, mpim:history, im:history |
| Read and write canvases | canvases:read, canvases:write |
| Read user profiles | users:read, users:read.email |
| Let the bot list channels | channels:read |
Copy Slack OAuth Credentials
Open Settings > Basic Information in your Slack app and copy the Client ID and Client Secret. Store the secret securely; you will paste it into the TrueFoundry MCP server OAuth configuration. If you reused an existing Slack app, also verify the following:- The redirect URL is
https://<tfy-control-plane-base-url>/api/svc/v1/llm-gateway/mcp-servers/oauth2/callback. - The user and bot scopes match the access you want to grant.
- Model Context Protocol is enabled under Agents & AI Apps.
Register Slack in TrueFoundry
Add a remote MCP server
In TrueFoundry, open MCP Gateway, click Add MCP Server, and select Connect any Remote MCP Server.
Configure the server
Use the following values:
| Field | Value |
|---|---|
| Name | slack |
| URL | https://mcp.slack.com/mcp |
| Description | Slack MCP server for searching messages, reading channels, and using Slack tools from agents. |
| Authentication | OAuth2 |
| Grant Type | Authorization Code |
| Authorization URL | https://slack.com/oauth/v2/authorize |
| Token URL | https://slack.com/api/oauth.v2.access |
| Client ID | Client ID from the Slack app |
| Client Secret | Client Secret from the Slack app |
| JWT Source | Access Token |
Add collaborators
Add the users or teams that should use Slack tools. Assign MCP Server Manager to administrators and MCP Server User to consumers.
Verify the Connection
For OAuth-based MCP servers, users must first open the server’s Tools section and click Connect Now. After OAuth succeeds, the Slack tools appear in the tools list. Users can then try those tools from the Agent Playground. Test write-capable tools only if you intentionally keptchat:write in the Slack app scopes.
Use Slack Safely with Agents
- Use per-user OAuth authorization so Slack permissions follow each user’s workspace access.
- Keep the Slack client secret in TrueFoundry and rotate it if it is exposed.
- Start with read-only scopes for broad rollouts, then add write scopes for trusted teams or virtual MCP servers.
- Use Virtual MCP Server to publish only the Slack tools each agent should call.
- Review Slack’s MCP security guidance before enabling Slack alongside other sensitive MCP servers.