The server itself exposes 21 tools, and some of them can write to your Slack account. Behind TrustGate an agent only sees the tools you allow, requests and responses are inspected, and every call is logged. Anything outside the allowlist is denied before it reaches Slack.

How is this different from connecting Slack MCP directly?

Connected directly, an agent sees every tool the server exposes and holds the credential itself. Through TrustGate you choose which tools each agent gets, and every call is logged against the agent that made it.

What if the Slack MCP API changes?

We track the Slack MCP schema, so the tool catalogue stays current. Tools you have already allowed keep working, and anything new stays denied until you enable it.

Can I give different agents different Slack tools?

Yes. Access is set per agent: one can get a handful of read tools, another the full set. You grant the whole MCP or single tools within it.

Where can I see what my agents did in Slack?

Every call is logged against the agent that made it, with the tool it used. Activity can be sent on to your own monitoring.

Do I need to run the Slack MCP server myself?

No. TrustGate connects to the Slack MCP server and sits in front of it. Your agent only talks to your TrustGate URL, never to Slack directly.

Connect Slack MCP to your AI agents, securely.

One secured endpoint for every Slack call your AI agents make, scoped per user, inspected, and logged.

Get started for free

Get a demo

Try Slack MCP now

What your agents can ask once Slack MCP is connected.

“What did the team decide about the launch date?”
“Draft a message for the project channel”
“Read the thread about the incident”

“Find the channel where design reviews happen”
“Schedule a reminder in the team channel for Monday”
“Who works on the platform team?”

Select the tools your AI agents can call

21 tools from the Slack MCP schema.

Showing 21 tools

slack_search_publicreadSearches for messages and files in public Slack channels only.
slack_search_public_and_privatereadSearches for messages and files in all Slack channels, including public channels, private channels, DMs, and group DMs.
slack_search_channelsreadSearch for Slack channels by name or description. Returns channel names, IDs, topics, purposes, and archive status.
slack_search_usersreadSearch for Slack users by name, email, or profile attributes such as department, role or title.
slack_search_emojisreadSearches the custom emoji available in the Slack workspace by name.
slack_read_channelreadReads messages from a Slack channel in reverse chronological order. To read DM history, use a user_id as channel_id.
slack_read_threadreadReads messages from a specific Slack thread: the parent message and all replies.
slack_read_user_profilereadRetrieves detailed profile information for a Slack user: contact info, status, timezone, organization, and role.
slack_get_reactionsreadRetrieves all emoji reactions on a specific Slack message.
slack_list_channel_membersreadLists the members of a Slack channel, group or group DM with profile details.
slack_send_messagewriteSends a message to a Slack channel or user. To DM a user, use their user_id as channel_id.
slack_schedule_messagewriteSchedules a message for future delivery to a Slack channel. Does not send immediately.
slack_send_message_draftwriteCreates a draft message in a Slack channel. The draft is saved to the user's Drafts and Sent without being sent.
slack_add_reactionwriteAdds an emoji reaction to a Slack message on behalf of the user.
slack_create_conversationwriteCreates a channel, DM or group DM on behalf of the user.
slack_create_canvaswriteCreates a Slack Canvas document from Canvas-flavored Markdown content.
slack_read_canvasreadRetrieves the markdown content and section ID mapping of a Slack Canvas document.
slack_update_canvashigh riskUpdates an existing Slack Canvas with markdown content. Replacing without a section ID overwrites the entire canvas.
slack_read_filereadReads a Slack file's content by file ID.
slack_get_file_upload_urlwriteGets a signed upload URL and file ID; the file bytes are then posted to that URL. The file stays hidden until the upload is completed.
slack_complete_file_uploadhigh riskFinalizes a file upload by file ID, optionally sharing the file to a channel with a message.

What Slack MCP exposes

Slack MCP groups its 21 tools into 5 categories, each with a suggested starting policy.

Category	Covers	Access	Suggested policy
Search	Message and file search across public or all conversations, plus channel, user and custom emoji lookup	Read	Prefer public search; require consent for private search
Read	Channel history, thread replies, user profiles, message reactions and channel members	Read	Limit to the channels the user can already see
Messaging	Sending, scheduling and drafting messages, adding reactions and creating conversations	Read / Write	Prefer drafts; require approval before sending
Canvases	Creating, reading and updating Slack canvases	Read / Write	Require approval for full-canvas replacement
Files	Reading file contents and the two-step file upload, which can share the file to a channel	Read / Write	Uploads can share files into channels; require approval before completing an upload with sharing