npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

markov-slack-mcp

v1750861100.9.0

Published

A Slack MCP server

Readme

slack-mcp-server

A MCP(Model Context Protocol) server for accessing Slack API. This server allows AI assistants to interact with the Slack API through a standardized interface.

Transport Support

This server supports both traditional and modern MCP transport methods:

  • Stdio Transport (default): Process-based communication for local integration
  • Streamable HTTP Transport: HTTP-based communication for web applications and remote clients

Features

Available tools:

  • slack_list_channels - List all conversations in the workspace (channels, DMs, group DMs)
  • slack_list_conversations - List conversations with flexible type filtering (public_channel, private_channel, mpim, im)
  • slack_post_message - Post a message to any Slack conversation as the authenticated user
  • slack_reply_to_thread - Reply to a message thread in any Slack conversation as the authenticated user
  • slack_get_channel_history - Get recent messages from any conversation you have access to
  • slack_get_thread_replies - Get all replies in a message thread from any conversation
  • slack_get_users - Retrieve basic profile information of all users in the workspace
  • slack_get_user_profile - Get a user's profile information
  • slack_get_user_profiles - Get multiple users' profile information in bulk (efficient for batch operations)
  • slack_search_messages - Search for messages in the workspace

Important Notes

  • User Authentication: All operations (reading and writing) use the user token, providing full access to conversations you can see.
  • DM Support: You can send and read DMs to/from any user without restrictions.
  • No Channel Membership Required: Since we use the user token, you can read messages from any channel you have access to.
  • Messages Appear From You: All posted messages and replies appear as coming from your user account.
  • Bot Token: Currently required by configuration but not actively used for any operations.

Quick Start

Installation

npm install -g markov-slack-mcp

Or use with npx (no installation required):

npx markov-slack-mcp

Configuration

You need to set the following environment variables:

  • SLACK_BOT_TOKEN: Slack Bot User OAuth Token
  • SLACK_USER_TOKEN: Slack User OAuth Token (required for some features like message search)

You can also create a .env file to set these environment variables:

SLACK_BOT_TOKEN=xoxb-your-bot-token
SLACK_USER_TOKEN=xoxp-your-user-token

Usage

Start the MCP server

Stdio Transport (default):

npx markov-slack-mcp

Streamable HTTP Transport:

npx markov-slack-mcp -port 3000

You can also run the installed module with node:

# Stdio transport
slack-mcp-server

# HTTP transport  
slack-mcp-server -port 3000

Command Line Options:

  • -port <number>: Start with Streamable HTTP transport on specified port
  • -h, --help: Show help message

Client Configuration

For Claude Desktop (using Claude Code CLI):

claude mcp add slack -s local \
  -e SLACK_BOT_TOKEN=<your-bot-token> \
  -e SLACK_USER_TOKEN=<your-user-token> \
  -- npx -y markov-slack-mcp slack-mcp-server

For Manual MCP Configuration (Claude Desktop, etc.):

{
  "slack": {
    "command": "npx",
    "args": [
      "-y",
      "markov-slack-mcp",
      "slack-mcp-server"
    ],
    "env": {
      "SLACK_BOT_TOKEN": "<your-bot-token>",
      "SLACK_USER_TOKEN": "<your-user-token>"
    }
  }
}

For Streamable HTTP Transport (Web applications):

Start the server:

SLACK_BOT_TOKEN=<your-bot-token> SLACK_USER_TOKEN=<your-user-token> npx markov-slack-mcp -port 3000

Connect to: http://localhost:3000/mcp

See examples/README.md for detailed client examples.

Implementation Pattern

This server adopts the following implementation pattern:

  1. Define request/response using Zod schemas

    • Request schema: Define input parameters
    • Response schema: Define responses limited to necessary fields
  2. Implementation flow:

    • Validate request with Zod schema
    • Call Slack WebAPI
    • Parse response with Zod schema to limit to necessary fields
    • Return as JSON

For example, the slack_list_channels implementation parses the request with ListChannelsRequestSchema, calls slackClient.conversations.list, and returns the response parsed with ListChannelsResponseSchema.

Development

Available Scripts

  • npm run dev - Start the server in development mode with hot reloading
  • npm run build - Build the project for production
  • npm run start - Start the production server
  • npm run lint - Run linting checks (ESLint and Prettier)
  • npm run fix - Automatically fix linting issues

Contributing

  1. Fork the repository
  2. Create your feature branch
  3. Run tests and linting: npm run lint
  4. Commit your changes
  5. Push to the branch
  6. Create a Pull Request