Slack MCP Server - Complete Implementation

Created By
yeoamloga year ago
Overview

what is Slack MCP Server?

Slack MCP Server is a complete implementation of a Slack API integration server using FastMCP v2, designed to facilitate communication and task management within Slack.

how to use Slack MCP Server?

To use the Slack MCP Server, clone the repository, set up the environment variables, and run the server. You can then interact with the server using various API calls to send messages, upload files, and manage timers.

key features of Slack MCP Server?

  • ✅ Full UTF-8 Korean support for all messages
  • ✅ Dual token system (Bot Token + User Token) for comprehensive functionality
  • ✅ Smart file upload with automatic size-based optimization
  • ✅ Pomodoro timer with automatic notifications
  • ✅ Asynchronous processing for high performance
  • ✅ Detailed error handling for all API calls

use cases of Slack MCP Server?

  1. Sending messages to channels or direct messages (DMs)
  2. Uploading files with optimized methods based on file size
  3. Managing tasks with a Pomodoro timer
  4. Retrieving channel history and user information

FAQ from Slack MCP Server?

  • Can I use this server for all Slack functionalities?

Yes! The server supports a wide range of Slack API functionalities including messaging, file uploads, and user management.

  • Is there a limit on file uploads?

Yes, the maximum file size for uploads varies based on the token used; Bot Token allows up to 100MB, while User Token allows up to 1GB.

  • How do I set up the server?

Follow the installation instructions in the README to clone the project, set environment variables, and run the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yeoamlog
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago