העמוד הזה עוד לא תורגם; מוצגת הגרסה באנגלית.

בטא בקרוב. הפיצ׳ר עדיין בפיתוח, ולכן שמות ופרטים עשויים להשתנות לפני השחרור.

Slack connection

Connect Slack once and agents can search messages, read channels and threads, look people up and post for you. Posting always asks first.

Connect

  1. Open the MCP tool window (Ingot: Rules, Commands & MCP Servers). The Slack card is at the top of the server list.
  2. Click Connect.
  3. Paste a token into Slack token: a user token (xoxp-…) or a bot token (xoxb-…) from your Slack app's OAuth & Permissions page. No app yet? Use Create a Slack app.
  4. Click Save & Connect.

The card then shows Connected · 12 tool(s). Agents see the tools as slack/<tool>.

Card saysWhat to do
Not connectedclick Connect
Turned off in MCP serversclick Turn on
Token missing. Connect again.click Reconnect and paste the token
Slack rejected the token. Check it and connect again.the token is wrong, revoked, or the app lacks a permission it needs

Disconnect removes the server and deletes the token.

Posting always asks

Any Slack tool that changes something (send, post, reply, schedule, edit, delete, react, upload, invite, pin and similar) shows an approval card every time, with no Always Run, even if you allowed MCP tools before:

Post to Slack (slack_send_message): #releases: v1.4 is out

Reading tools (search, read a channel, list people) use the usual MCP approval card.

Where the token is stored

Ingot writes a global server named slack to ~/.ingot/mcp.json with a placeholder:

{
  "mcpServers": {
    "slack": {
      "url": "https://mcp.slack.com/mcp",
      "headers": { "Authorization": "${keychain}" }
    }
  }
}

The real token goes to Ingot's local key file, ~/.ingot/keystore.json, which only your user can read. It never lands in a project or a config file you might commit.

Other servers, including your own, are covered in MCP.