Communication

Slack

Send messages and manage channels.

Connect stays on CybrLink. Signed-out visitors go to sign-in. Signed-in visitors open the connect host at connect.cybrlink.dev.

OAuthScoped proxy

Connect through OAuth

The client approves access on the provider's authorization screen. CybrLink stores the resulting credential through Nango and exposes only scoped, auditable agent access.

Slack connection guide
Connect in portal

Step 1

Open OAuth connect

Step 2

Approve provider access

Step 3

Create a scoped MCP/API key

Sample request

// 1. Mint a session token for the end user
const session = await link.connect.session({
  integrationKey: "slack",
  userId: "u_42",
});

// 2. After the user completes OAuth, proxy a request
const res = await link.proxy("slack", "u_42", {
  method: "GET",
  endpoint: "/api/v1/me",
});

More in this category

Typed agent tools

6 typed actions your SI (super intelligence) agents can run through CybrLink's MCP server once Slack is connected.

Slack + SI agents: common questions

How do I connect Slack to an SI agent?
Create a free CybrLink account, open the dashboard, and click Connect on Slack. You authorize once with OAuth; CybrLink stores the credential in its token vault and your agent reaches Slack through the CybrLink MCP server or the agent proxy API. The credential itself is never placed in the model's context.
Does Slack work with Claude, GPT, and other MCP clients?
Yes. CybrLink exposes a remote MCP (Model Context Protocol) server, so any MCP-capable client or agent framework — including Claude, OpenAI-based agents, and custom agents — can call Slack once you've connected it. Non-MCP agents can use the authenticated HTTP proxy instead.
Is it safe to give an SI agent access to Slack?
CybrLink scopes every connection to the permissions you grant, keeps tokens out of the model, logs each call to an activity audit trail, and lets you revoke the Slack connection at any time from the dashboard.