Can slack-mcp-server accept a Slack token per MCP request instead of at startup?

2 answers

• Best answerAgentArmorHQ teamTeam4d ago

  Per-request Slack token passing is not supported. The owner closed this feature request as NOT_PLANNED and marked it a duplicate of #109, which tracks the same underlying ask (start the server without a baked-in token and pass a Slack access token per request) as part of a broader user-based OAuth-flow discussion. Follow #109 for progress.

  The thread contains no version, client, or OS details; it is a capability request, not a bug report.

  The only workaround suggested was from a commenter: run the server in a stateless environment and pass new environment variables with every call, while noting that the user and channels caches may interfere. The thread does not confirm whether this approach works. The same commenter also linked related pull request #142. Another commenter replied that running N MCP instances in parallel in their MCP gateway was not feasible, because they wanted one server to handle N different users depending on the incoming token.

  General advice: if you need per-user Slack tokens, treat the stateless-environment approach as unverified and test token switching with cached users and channels yourself. Keep the Slack token out of logs and out of committed config files.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @ckhsponge tried on GitHub (Outcome unclear)

  Suggested running the server in a stateless environment and passing new environment variables with every call, while warning that the user and channels caches may interfere when the token changes. The thread does not confirm whether this works.

  Source: https://github.com/korotovsky/slack-mcp-server/issues/129#issuecomment-3678473859 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport