Skip to content

Slack

Artific Connect · Slack gives a key Slack's own tools: messages, threads, canvases and search. It installs from the Marketplace like any other bundle.

What you get

One toolset, slack, holding everything Slack's own MCP server offers, plus a skill that tells the model how a channel and a thread are named. Attach the toolset to a key and the tools are there.

Signing in

The tools act as the person the turn is for, through that person's own Slack account, scoped to the granular permission each tool needs. Two things follow:

  • a request must name a user; one that names nobody is told so instead of calling a tool;
  • each person signs in once, from the bundle's page in the console or through the link the model is given the first time it tries.

The consent screen says Artific: the application is this deployment's, registered once by its operator, and no organisation registers one of its own.

Before it works

Your administrator has to allow both hosts the bundle dials in the key's own egress policy:

  • mcp.slack.com — the MCP server itself;
  • slack.com — where a person signs in and where the code is exchanged for a token.

Slack also requires every MCP client application to be listed in the Slack App Directory (or be an internal app usable by one workspace only, which does not fit a deployment serving many organisations); until the operator's submission is approved, no workspace can use this bundle at all, whatever its own admin approves. A workspace's own admin approves the application a second time, per workspace, before its people can sign in.

If the operator has not registered and published the Artific application at Slack yet, the install waits: the bundle sits at needs configuration and names what it is waiting for.

Good to know

  • Verified 2026-09-24 on docs.slack.dev: the server is https://mcp.slack.com/mcp. GA since 2026-02-17.
  • Access is scoped per tool: searching messages needs search:read.*, sending a message needs chat:write, and a tool answering "missing scope" names exactly what to add to the application's own OAuth scopes.
  • Rate limits are per method and per workspace; a "not found" on a channel usually means the connected account is not a member of it.
  • The mark: this bundle's card still uses Artific's own placeholder. Slack's brand guidelines do not say whether an integration marketplace card is a covered use and invite anyone unsure to contact Slack first, which this deployment has not done (checked 2026-09-24).