Integration · For administrators

Bring your agents into Slack.

Enable Slack once for your organization. Members connect their own accounts, agents act as them, and you decide, tool by tool, what runs unattended and what waits for a human.

Add to Slack

Add to Slack opens Lunen's MCP Registry with Slack selected, signing you in first if needed. Enabling a server needs the administrator role in your Lunen organization.

What you are enabling.

Slack joins Lunen through Slack's own hosted MCP server. Enabling it makes it connectable; it grants nothing by itself.

  • No bot, no workspace-wide token

    Slack is connected per member, with that member's own user token. An agent acting for someone sees exactly what they can see in Slack, and nothing more.

  • Nothing to register in Slack

    Lunen manages the Slack app and its OAuth client. If your workspace restricts app installs, a Slack admin approves Lunen once; otherwise there is no Slack-side setup.

  • Every tool is a policy decision

    Each Slack tool is set to Allow or Approve. Allow runs unattended; Approve pauses the run and puts the call, inputs visible, in front of a reviewer first.

  • Everything on the record

    Every Slack tool call lands in the audit log with who acted, which agent ran, what was approved, and what it touched.

Enable Slack in four steps.

Three for you, one for your members. Lunen is in early access, so your organization needs a Lunen account first.

  1. 1Administrator

    Open Slack in the MCP Registry

    Settings, then MCP Registry, lists every server your organization could reach. Find Slack and choose Configure. The Add to Slack button on this page opens that panel directly.

  2. 2Administrator

    Switch it on

    Flip the enable toggle. There is no OAuth client to register and no Needs setup checklist: Slack is ready as soon as it is enabled, and its tools appear in the catalog.

  3. 3Administrator

    Set the policy

    In Settings, then Policies, decide each Slack tool: Allow the reads (search, history, people), keep posting and canvas edits on Approve until an agent has earned it. New tools arrive disabled, never pre-allowed.

  4. 4Members

    Let members connect

    Each member opens Connected Services and chooses Connect next to Slack. Slack asks them to sign in and approve the permissions, then returns them to Lunen. From then on, agents acting for them use that connection.

Add to SlackRead the full guide in the docs

Allow the reads. Approve the writes.

Slack's tools split cleanly. Start here, then loosen a write once an agent has shown its work.

  • Reads

    Allow

    Search channels, direct messages, and files; read message history; look up people. Limited to what the connected member can already see.

  • Writes

    Approve

    Post messages as the member, and create or edit canvases. A reviewer sees the exact message or content before it reaches the channel.

How policies resolve, who may change them, and what a reviewer sees: Policy & approvals.

What each member grants

When a member connects, Slack asks them for a user token scoped to their own access. The consent screen lists permissions to:

  • Read and search messages in public channels, private channels, direct messages, and group messages they belong to
  • Search files and people in the workspace, including email addresses
  • Send messages on their behalf
  • Read, create, edit, and remove canvases

What Lunen stores, and turning it off

Member tokens are stored encrypted in a dedicated secrets vault. The results of each tool call are kept with the conversation or run that requested them, and the audit log records that the call happened.

Switch Slack off in the MCP Registry and its tools leave every agent's reach. A member's Disconnect in Connected Services deletes their token immediately, and a Slack admin can revoke Lunen from Slack's app management page.

Need a hand?

The docs at docs.lunen.ai cover the registry, policies, and approvals. For anything else, email hello@lunen.ai.