Slack

Not in the app yet. Slack’s server needs an app with a client id and a client secret, and Gantry has nowhere safe to keep a secret on your machine. It waits for that question to be answered rather than for a release. Everything below is what it will do when it lands. Meanwhile you can add any MCP server yourself under Settings → Connectors, and saying you want this one moves it up the list.

Read channels and threads, search history, and post messages. Posting is an external write and asks first outside Auto.

What it can do

Examples of the tools the agent gets from this connector. Each call shows up in the activity feed with its input and result.

1. slacklist_channels
2. slackread_thread #releases
3. slacksearch_messages "deploy failed"
4. slackpost_message

How it connects

Sign-in

Sign in with your account (OAuth). Installing opens Slack in your browser to sign in once. The token comes back to Gantry over a local callback and is stored encrypted on your machine.

Runs as

Remote MCP server, reached over HTTPS. An MCP server hosted by the service, reached over HTTPS. Nothing runs on your machine beyond Gantry.

Permissions

Reads run in every mode. Writes outside your folders, messages and anything destructive follow the chat's permission mode: they ask in Manual and Auto-edit, and are judged by the guard model in Auto. How permissions work

How it will install

1. 1

   Open Connectors in the sidebar. The catalog ships with the app; nothing is downloaded until you ask.

2. 2

   Find Slack and choose Install. Your browser opens to sign in; close it when it says you can.

3. 3

   Attach it to a chat, or leave it available to every chat in a project. The agent sees its tools from then on.