slack-mcp-claude-auth
Provides a proxy to Slack's MCP endpoint, enabling AI agents to perform Slack actions such as searching users, reading threads, and other Slack operations via the official Slack MCP tools.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@slack-mcp-claude-authsearch for users with name Alice"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 buildRelated MCP server: Claude Code Slack Channel
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 slackIf 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.jsoncache contains only tool metadata, no Slack tokens
expired cache is used as fallback if refresh fails
set
SLACK_MCP_TOOL_LIST_CACHE_MS=0to disable wrapper cache
Tool names:
official Slack tools are named
slack_search_users,slack_read_thread, etc.pi-mcp-adapteralso prefixes tools with server nameslack_wrapper strips the official redundant
slack_prefix before exposing tools, so Pi names becomeslack_search_users, notslack_slack_search_usersdisable 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-credentialsJSON 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/mcpOn token refresh, wrapper writes refreshed access/refresh token back into the same Claude Code keychain JSON by default. Disable with:
SLACK_MCP_WRITEBACK=0Common failure
Slack token refresh HTTP 400: invalid_grantClaude 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 |
|
|
|
|
| Claude Code Slack client id |
| Claude Code Slack MCP credential key |
|
|
| current macOS username |
|
|
|
|
|
|
|
|
|
|
|
|
This server cannot be deployed
Maintenance
Related MCP Connectors
- QuallaaOAuthcom.quallaa
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
Real-time chat for AI agents. Claude Code, Cursor, Cline and Codex join channels over MCP.
WhatsMCP connects Claude and other MCP-compatible AI agents directly to WhatsApp. Send and receive text, images, documents, and voice notes; manage groups (create, add/remove members, promote admins); look up contacts and profiles; follow channels; and read call and message history — all through a standard MCP interface. For voice use cases, WhatsMCP offers SIP-based calling plans (inbound-only, or full inbound/outbound) so AI voice agents can answer and place WhatsApp calls, plus low-latency WebSocket integrations with voice agent providers like ElevenLabs. Multiple WhatsApp accounts can be paired and managed per workspace, with webhook support for real-time inbound message delivery to your own infrastructure.
Let Claude or ChatGPT search, read and send your WhatsApp messages over MCP. OAuth sign-in.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for Slack integration, allowing Claude to interact with your Slack workspace.32,508 npmMIT
- AlicenseAqualityDmaintenanceMCP server that connects Claude Code to Slack, allowing two-way communication via Slack Socket Mode without tunnels.1MIT
- FlicenseNot gradedqualityCmaintenanceMCP proxy that bridges Mendix Marketplace's Streamable HTTP endpoint to stdio, enabling Claude Code and other stdio-only MCP clients to access Mendix Marketplace tools and prompts dynamically.-
- AlicenseAqualityAmaintenanceLocal MCP stdio bridge to Slack's hosted MCP server, enabling agents to use Slack tools (send messages, search, history, canvas, etc.) via local OAuth and token refresh.868 npmMIT