Which integrations are available for this server?

Allows searching Slack channels and messages, listing available workspace channels, and retrieving detailed message history from specific channels.

How do I use Slack MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Slack MCP Server find messages about the API update in #development" 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 Server

by nikhilchintawar

Overview Schema Related Servers Score Discussions

TypeScript

Remote

Slack MCP Server

A Model Context Protocol (MCP) server for searching Slack channels and messages.

Features

list_channels - List available Slack channels in the workspace
search_messages - Search for messages across channels using text matching
get_channel_history - Get message history from a specific channel

Related MCP server: Slack MCP Server

Installation

Using npx (Recommended)

No installation required. Add directly to your config:

Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": ["-y", "github:nikhilchintawar/slack-mcp"],
      "env": {
        "SLACK_BOT_TOKEN": "xoxb-your-token-here"
      }
    }
  }
}

Claude Code (~/.claude/settings.json):

{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": ["-y", "github:nikhilchintawar/slack-mcp"],
      "env": {
        "SLACK_BOT_TOKEN": "xoxb-your-token-here"
      }
    }
  }
}

Manual Installation

# Clone the repository
git clone https://github.com/nikhilchintawar/slack-mcp.git
cd slack-mcp

# Install dependencies
npm install

# Build
npm run build

Then add to your config:

{
  "mcpServers": {
    "slack": {
      "command": "node",
      "args": ["/absolute/path/to/slack-mcp/build/index.js"],
      "env": {
        "SLACK_BOT_TOKEN": "xoxb-your-token-here"
      }
    }
  }
}

Configuration

Config File Locations

Claude Desktop (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json
Claude Desktop (Windows): %APPDATA%\Claude\claude_desktop_config.json
Claude Code: ~/.claude/settings.json

Environment Variables

Variable	Required	Description
`SLACK_BOT_TOKEN`	Yes	Slack Bot User OAuth Token
`SLACK_CHANNELS`	No	Comma-separated list of allowed channels (restricts searches)
`SLACK_DEFAULT_CHANNEL`	No	Default channel ID for operations

Channel Restrictions

Use SLACK_CHANNELS to restrict which channels can be searched. When configured:

Searches without a channel specified will search all allowed channels
Searches with a specific channel will validate it's in the allowed list
get_channel_history will only work with allowed channels

{
  "env": {
    "SLACK_BOT_TOKEN": "xoxb-your-token",
    "SLACK_CHANNELS": "general,engineering,support"
  }
}

Slack App Setup

Create a Slack App at https://api.slack.com/apps
Go to "OAuth & Permissions"
Add the following Bot Token Scopes:
- channels:read - List public channels
- channels:history - Read messages from public channels
- groups:read - List private channels (optional)
- groups:history - Read messages from private channels (optional)
Install the app to your workspace
Copy the "Bot User OAuth Token" (starts with xoxb-)
Important: Add the bot to each channel you want to search (right-click channel → "Open channel details" → "Integrations" → "Add apps")

Usage Examples

Once configured, you can use natural language to interact with Slack:

"List all channels in my Slack workspace"
"Search for messages about deployment in #engineering"
"Show me the last 50 messages from #general"
"Find messages from @john about the API"
"Search for error messages from last week"

Available Tools

`list_channels`

List available Slack channels in the workspace.

Parameter	Required	Description
`includePrivate`	No	Include private channels (default: false)
`includeArchived`	No	Include archived channels (default: false)
`limit`	No	Max results (default: 100, max: 1000)

`search_messages`

Search for messages across Slack channels using text matching. Fetches channel history and filters by query.

Parameter	Required	Description
`query`	Yes	Search text (case-insensitive). Use `\|` for OR, spaces for AND
`channel`	No	Channel ID or name. If not set, searches all `SLACK_CHANNELS`
`after`	No	Search messages after date (YYYY-MM-DD or ISO 8601)
`before`	No	Search messages before date (YYYY-MM-DD or ISO 8601)
`limit`	No	Max results (default: 20, max: 100)

Query examples:

error - messages containing "error"
error warning - messages containing both "error" AND "warning"
error | warning - messages containing "error" OR "warning"

`get_channel_history`

Get message history from a specific Slack channel.

Parameter	Required	Description
`channel`	No	Channel ID (uses env var default)
`oldest`	No	Start time (Unix timestamp or ISO date)
`latest`	No	End time (Unix timestamp or ISO date)
`limit`	No	Max results (default: 100, max: 1000)
`includeThreadReplies`	No	Include thread replies (default: false)

Development

# Watch mode for development
npm run dev

# Build for production
npm run build

# Test with MCP Inspector
SLACK_BOT_TOKEN=xoxb-your-token \
  npx @modelcontextprotocol/inspector node build/index.js

License

MIT

Available Tools

3 tools

get_channel_historyC

Get message history from a specific Slack channel

ParametersJSON Schema

Name	Required	Description
`channel`	No	Channel ID to fetch history from. Uses SLACK_DEFAULT_CHANNEL if not provided.
`oldest`	No	Start of time range (Unix timestamp or ISO date)
`latest`	No	End of time range (Unix timestamp or ISO date)
`limit`	No	Maximum number of messages to return
`includeThreadReplies`	No	Include thread reply messages

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but doesn't cover critical aspects like whether this is a read-only operation, rate limits, authentication needs, or what the return format looks like. For a tool with 5 parameters and no output schema, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without any fluff or redundancy. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a 5-parameter tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits, return values, and usage context, making it incomplete for effective agent operation despite the concise structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, with all parameters well-documented in the input schema. The description doesn't add any parameter-specific information beyond what's in the schema, so it meets the baseline of 3 where the schema handles the heavy lifting without extra value from the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and resource 'message history from a specific Slack channel', making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'search_messages' which might also retrieve messages, leaving room for improvement in distinguishing between them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'search_messages' or 'list_channels'. The description lacks context about use cases, prerequisites, or exclusions, leaving the agent without direction on tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_channelsB

List available Slack channels in the workspace

ParametersJSON Schema

Name	Required	Description
`includePrivate`	No	Include private channels (requires appropriate scopes)
`includeArchived`	No	Include archived channels
`limit`	No	Maximum number of channels to return

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'List' implies a read operation, the description doesn't address authentication requirements, rate limits, pagination behavior, or what 'available' means in practice. It lacks details about the return format or potential errors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with no annotations and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details about behavioral traits, usage context, and output format. The high schema coverage helps, but the description doesn't fully compensate for missing annotation and output information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with all three parameters well-documented in the schema. The description doesn't add any parameter-specific information beyond what the schema provides, so it meets the baseline for high schema coverage without compensating with extra context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('available Slack channels in the workspace'), providing specific functionality. However, it doesn't explicitly distinguish this tool from its siblings (get_channel_history, search_messages), which focus on message history and search rather than channel listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention scenarios where list_channels is appropriate compared to get_channel_history or search_messages, nor does it discuss prerequisites or constraints beyond what's implied by the parameters.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_messagesC

Search for messages across Slack channels using query syntax

ParametersJSON Schema

Name	Required	Description
`query`	Yes	Search query string (case-insensitive text match)
`channel`	No	Channel ID or name to search in. If not provided, searches all configured SLACK_CHANNELS.
`after`	No	Search messages after this date/time (YYYY-MM-DD or ISO 8601)
`before`	No	Search messages before this date/time (YYYY-MM-DD or ISO 8601)
`limit`	No	Maximum number of matching messages to return

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'query syntax' but doesn't explain what that includes, nor does it cover important aspects like permissions needed, rate limits, pagination behavior, or what happens when no results are found. For a search tool with 5 parameters, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without any fluff. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a search tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits, result formatting, error handling, and differentiation from siblings, making it inadequate for full agent understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents all 5 parameters. The description adds minimal value by mentioning 'query syntax' but doesn't elaborate on syntax details or provide additional context beyond what the schema already specifies. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('search') and resource ('messages across Slack channels'), and mentions 'query syntax' which adds specificity. However, it doesn't explicitly differentiate from sibling tools like 'get_channel_history' or 'list_channels', which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'get_channel_history' or 'list_channels'. It mentions 'query syntax' but doesn't explain what that entails or when it's preferable to other tools, leaving the agent with no usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

3 tool updatesv1.0.0Feb 21, 2026
- First observedget_channel_history
- First observedlist_channels
- First observedsearch_messages

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: get_channel_history retrieves messages from a specific channel, list_channels enumerates available channels, and search_messages performs cross-channel searches. There is no overlap in functionality, making tool selection straightforward for an agent.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern (get_channel_history, list_channels, search_messages), using snake_case uniformly. The verbs (get, list, search) are appropriate and predictable, enhancing readability and usability.

Tool Count3/5

With only 3 tools, the server feels thin for a Slack integration, as it lacks essential operations like sending messages, managing users, or handling reactions. While the tools are well-defined, the count is borderline low for the domain's typical scope.

Completeness2/5

The toolset is significantly incomplete for a Slack server, missing core CRUD operations such as sending messages, creating channels, updating messages, or deleting content. This creates dead ends for agents trying to perform common Slack workflows, likely leading to failures.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Remote MCP A
com.remote-mcp.mcp
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
Developer Tools Search Agent Orchestration
13
CustomGPT.ai
ai.customgpt.mcp
The CustomGPT.ai MCP server is a fully managed, RAG-powered endpoint that connects large language models with private knowledge bases and external data sources. It provides tools for retrieval-augmented generation queries (send_message), data ingestion (upload_file), and source listing, enabling AI agents to query private documents like PDFs with high accuracy and real-time citations.
RAG Systems Knowledge & Memory Search
2
LLMemoryOAuth
io.github.meir-may
Search your AI chat history (ChatGPT, Claude, Codex) from any MCP client. Remote, private, read-only
Search Knowledge & Memory
2
Unified.to MCP Server C
to.unified.docs
Unified MCP Server is a remote MCP connector for AI agents and vertical AI products that provides access to 22,000+ authorized SaaS tools across 400+ integrations and 24 categories directly inside LLMs (Claude, GPT, Gemini, Cohere). Tools operate only on explicitly authorized customer connections, enabling agents to safely read and write against live third-party systems.
App Automation Agent Orchestration Developer Tools
2

Related MCP Servers

Slack Search MCP Server
Communication Search
takuya0206
F
license
Not graded
quality
D
maintenance
An MCP server that enables LLMs to access Slack's search functionality to retrieve users, channels, messages, and thread replies from a Slack workspace.
Updated a year ago (2025-03-14 07:34 UTC)
4
-
Slack MCP Server
Communication Search Developer Tools
paterapatera
A
license
Not graded
quality
D
maintenance
An MCP server that enables AI agents to search and retrieve messages within a Slack workspace using the Slack Web API. It supports specific channel filtering and includes built-in rate limit handling for efficient message discovery.
Updated 7 months ago (2026-02-19 00:22 UTC)
54
MIT
MCP Slack Python
Communication Developer Tools
minji337
F
license
Not graded
quality
D
maintenance
An MCP server that enables interaction with Slack workspaces through tools for managing channels, sending messages, and retrieving user profiles. It leverages the Slack API and FastMCP to provide functionalities like message history lookup and reaction management.
Updated 8 months ago (2026-01-17 17:44 UTC)
1
-
Slack MCP Server
Communication App Automation
sdancy10
A
license
Not graded
quality
D
maintenance
This MCP server provides integration with the Slack API via HTTP transport, allowing for channel management and message operations. It enables users to list channels, send or edit messages, search message history, and retrieve user information through standardized tools.
Updated 7 months ago (2026-02-05 17:41 UTC)
54
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nikhilchintawar/slack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server