Skip to main content
Slack is a messaging platform for teams. TrueFoundry ships it as a fully managed MCP server, so your agents can search conversations, read channels and threads, send messages, and work with canvases without any infrastructure setup on your end. You add it from the TrueFoundry catalog, authorize once via OAuth2, and the endpoint is immediately available to every MCP-compatible client you use. Slack is provisioned as a TrueFoundry Managed MCP — the platform manages its URL, auth, scopes, and credentials. For how managed servers are provisioned and kept up to date, see TrueFoundry Managed MCPs. To register your own Slack app instead, see Slack MCP Server.

​
How TrueFoundry Manages the MCP Server

TrueFoundry’s MCP Gateway acts as a reverse proxy between your agents and MCP servers like Slack. When you add Slack as a managed MCP, TrueFoundry handles:
  • Authentication — Agents authenticate once to the TrueFoundry MCP Gateway. The AI Gateway handles outbound auth to Slack. Authorization happens directly between your account and your Slack workspace through the OAuth2 flow; TrueFoundry does not receive your Slack credentials.
  • Tool-level access control — You can selectively enable or disable individual Slack tools per team from the TrueFoundry UI.
  • Audit trail — Every tool invocation is traced with the calling user, tool name, input payload, and latency. Traces export via OpenTelemetry to your observability stack.
  • Guardrails — TrueFoundry’s guardrail hooks apply at mcp_pre_tool (before a tool is invoked) and mcp_post_tool (after the tool returns), letting you enforce content policies on Slack requests and results in real time.

​
Adding Slack to TrueFoundry

1

Open the MCP Server catalog

Navigate to MCP Servers in the TrueFoundry sidebar and click Add new MCP Server. On the next screen, select Connect TrueFoundry Managed MCPs — this opens the catalog of pre-vetted, fully configured MCP servers managed by TrueFoundry.
Add new MCP Server picker with the Connect TrueFoundry Managed MCPs option at the top
2

Add Slack

Click + Add on Slack. It appears as Slack [Managed] in your MCP Servers list.
MCP Servers list with Slack [Managed] at the top
3

Authenticate

The Tools tab shows that you’re not connected yet. Click Connect Now.
Slack Managed MCP server detail page with the Tools tab showing You're not connected and a Connect Now button
An authorization popup appears showing the MCP client name, the TrueFoundry website, and the redirect URI (https://auth.truefoundry.com/mcp/oauth2/callback). Review the details and click Approve — you’ll then be redirected to authenticate with your Slack workspace and grant access.
TrueFoundry does not receive your Slack credentials — the authorization is between your account and Slack directly.
OAuth authorization popup requesting access, showing the redirect URI and an Approve button before redirecting to the Slack workspace
4

Verify tools

After approving, the Tools tab populates with Slack’s available tools — searching messages and users, reading channels and threads, sending and scheduling messages, and working with canvases. Each tool shows its description and a Try button so you can test it before wiring it into an agent. Tools are labeled Read-only or Destructive so you can see at a glance which ones modify data.
Slack Tools tab populated with the available tools after a successful OAuth2 connection, each labeled Read-only or Destructive

​
Available Tools

The Slack managed MCP server exposes the following tools. Each tool acts with the permissions of the Slack user who authorized the connection, so agents can only see and do what that user can.

​
Connecting to an MCP Client

TrueFoundry exposes the Slack MCP server over HTTP transport. The endpoint is specific to your TrueFoundry tenant, so don’t construct it by hand — copy the exact URL and ready-to-paste connection commands from the How To Use tab on the Slack server detail page. The How To Use tab generates connection instructions for every major client, including Cursor, VS Code, Claude Code, Claude Web, Claude Desktop, Windsurf, Codex, and the Python and TypeScript MCP SDKs. Pick your client, copy the snippet, and paste it in. Click Show API Key on that tab to retrieve the API key if your client requires it as a header.
Slack How To Use tab showing connection commands for multiple MCP clients

​
Using Slack from an Agent

Once connected, ask your agent to work with Slack in plain language. For example:
  • “Summarize what was discussed in #release-planning this week.”
  • “Find the latest thread about the on-call handoff and post a short update in #eng-oncall.”
  • “Create a canvas with the action items from today’s standup.”
The agent picks the matching Slack tools, and every call is recorded in the audit trail.

​
Using the Tool Playground

Before deploying an agent, you can test any Slack tool directly in TrueFoundry:
1

Open a tool

On the Slack MCP server detail page, click Try next to any tool — for example slack_search_channels.
2

Fill in the inputs

Provide the tool’s inputs. For slack_search_channels, enter a search term such as engineering.
3

Execute and inspect

Click Execute Tool and inspect the JSON output in the right panel.

​
Tool Metrics

The Metrics tab on the Slack server detail page shows per-tool usage data: invocation count, latency distribution, and error rates. Use this to monitor which tools your agents are using and whether any tool is producing errors in production.

​
Disabling Individual Tools

If your use case only needs a subset of Slack’s tools, you can disable the rest from the Tools tab. Each tool has a toggle to enable or disable it. Disabled tools are not callable by agents — they will not appear in the tool list returned to the MCP client. This reduces the tool surface exposed to the agent and avoids unnecessary calls — for example, disabling slack_send_message and slack_update_canvas to keep an agent read-only.

​
Disconnecting Slack

To remove your authorization, click Disconnect at the top of the Slack server detail page. TrueFoundry deletes your stored tokens and agents can no longer call Slack tools on your behalf until you connect again. To also revoke the grant on Slack’s side, remove the app from your workspace’s Manage apps page in Slack. Tenant admins can remove every user’s stored credentials at once with Revoke all tokens.

​
Data and Privacy

TrueFoundry uses the data returned by Slack only to carry out the tool calls your agents make, and does not use it to train AI models. For details on what is collected and how long it is kept, see the TrueFoundry Privacy Policy.