Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
Your own AI agent, running 24/7 with QwikClaw logoYour own AI agent, running 24/7 with QwikClaw

QwikClaw sets up and runs an always-on OpenClaw agent for you. One click, no config files, no server setup.

Deploy now
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 47,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

Local stdio MCP proxy for the official Slack MCP endpoint, using Claude's Slack plugin for authentication to enable Slack integration via MCP without needing a custom Slack app.

README.md

slack-mcp-claude-auth

Local stdio MCP proxy for the official Slack MCP endpoint.

Intended to be used with the Pi Coding Agent and the pi-mcp-adapter extension installed. Only for MacOS. It uses Claude's official Slack plugin for authorisation flow so one doesn't need to create its own Slack application with its own client ID.

At first launch and if refresh token is expired, an authorisation to the officila Slack plugin is needed via the Claude CLI. No Slack tokens are stored or shared anywhere. If token is refreshed, it's stored into the same keychain record like it would be done via official Claude's Slack plugin.

Build

npm install
npm run build

Pi MCP config

Add to ~/.pi/agent/mcp.json:

{
  "mcpServers": {
    "slack": {
      "command": "node",
      "args": ["/Users/k.babaev/Sources/_index-only/slack-mcp-claude-auth/dist/index.js"],
      "lifecycle": "lazy"
    }
  }
}

Then reload Pi and refresh metadata:

/reload
/mcp reconnect slack

If direct tools are disabled, use proxy:

mcp({ server: "slack" })
mcp({ search: "slack thread" })
mcp({ tool: "slack_read_thread", args: "{...}" })

Dynamic tool list

The wrapper implements MCP tools/list by calling official Slack MCP tools/list. Tool schemas, descriptions, and names come from Slack, not from this repo.

Tool list cache:

  • default TTL: 24 hours (SLACK_MCP_TOOL_LIST_CACHE_MS=86400000)
  • default path: ~/.cache/slack-mcp-claude-auth/tools.json
  • cache contains only tool metadata, no Slack tokens
  • expired cache is used as fallback if refresh fails
  • set SLACK_MCP_TOOL_LIST_CACHE_MS=0 to disable wrapper cache

Tool names:

  • official Slack tools are named slack_search_users, slack_read_thread, etc.
  • pi-mcp-adapter also prefixes tools with server name slack_
  • wrapper strips the official redundant slack_ prefix before exposing tools, so Pi names become slack_search_users, not slack_slack_search_users
  • disable with SLACK_MCP_STRIP_REDUNDANT_TOOL_PREFIX=0

If pi-mcp-adapter direct tools are enabled, adapter may also cache metadata; run /mcp reconnect slack and /reload after Slack changes tools or after changing prefix behavior.

Claude Code auth source

Credentials are read from macOS Keychain item:

  • service: Claude Code-credentials
  • JSON path: mcpOAuth["plugin:slack:slack|38801a7d845718b3"]

Defaults match current Claude Code Slack MCP auth:

SLACK_MCP_CLIENT_ID=1601185624273.8899143856786
SLACK_MCP_CLAUDE_CRED_KEY=plugin:slack:slack|38801a7d845718b3
SLACK_MCP_URL=https://mcp.slack.com/mcp

On token refresh, wrapper writes refreshed access/refresh token back into the same Claude Code keychain JSON by default. Disable with:

SLACK_MCP_WRITEBACK=0

Common failure

Slack token refresh HTTP 400: invalid_grant

Claude Code keychain refresh token is stale/invalid. Re-authorize Slack in Claude Code CLI, then retry /mcp reconnect slack in Pi.

Environment knobs

| Variable | Default | | --- | --- | | SLACK_MCP_URL | https://mcp.slack.com/mcp | | SLACK_TOKEN_ENDPOINT | https://slack.com/api/oauth.v2.user.access | | SLACK_MCP_CLIENT_ID | Claude Code Slack client id | | SLACK_MCP_CLAUDE_CRED_KEY | Claude Code Slack MCP credential key | | SLACK_MCP_KEYCHAIN_SERVICE | Claude Code-credentials | | SLACK_MCP_KEYCHAIN_ACCOUNT | current macOS username | | SLACK_MCP_REFRESH_BUFFER_MS | 300000 | | SLACK_MCP_SESSION_TTL_MS | 79200000 | | SLACK_MCP_TOOL_LIST_CACHE_MS | 86400000 | | SLACK_MCP_TOOL_LIST_CACHE_PATH | ~/.cache/slack-mcp-claude-auth/tools.json | | SLACK_MCP_STRIP_REDUNDANT_TOOL_PREFIX | 1 | | SLACK_MCP_WRITEBACK | 1 |

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Communication servers.