Connector plugin · listing tai42/connector-slackInstall
Permissions
Provides
slack
Connector — OAuth connector for Slack over Slack’s hosted MCP server.
Registers the slack connector: one OAuth connection per alias against Slack’s
hosted MCP server at https://mcp.slack.com/mcp. The plugin is pure descriptor
data and ships no package; the runtime’s connector engine runs the OAuth flow,
seals the tokens, and reaches the MCP server over Streamable HTTP.
Install
Install the descriptor into the running server with the CLI:connectors: entry:
manifest.yml
Create the Slack app
Create a Slack app and configure OAuth. The app must be directory-published or internal to your workspace — Slack refuses an unlisted app on this flow, and there is no dynamic client registration. These are USER-token endpoints:- authorize:
https://slack.com/oauth/v2_user/authorize - token:
https://slack.com/api/oauth.v2.user.access
{origin} is your deployment’s public origin
(or CONNECTORS_OAUTH_BRIDGE_URL when you run a shared bridge):
CONNECTORS_* settings — the key-encryption key
(CONNECTORS_KEK), the state HMAC key (CONNECTORS_STATE_HMAC_KEY), and the
redirect-URI allowlist (or CONNECTORS_OAUTH_BRIDGE_URL) — are shared by every
connector and are described in Connectors. The origin
you registered with Slack must appear in the redirect-URI allowlist, and it must
be https for anything but a local host.
Verify the rotating-token response (before release)
See also
- Connectors — the model, the token lifecycle, and the shared engine settings.
- Connect an OAuth provider — the end-to-end walkthrough.

