{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-sigmacomputingslack-mcp-server","slug":"npm-sigmacomputingslack-mcp-server","name":"@sigmacomputing/slack-mcp-server","type":"mcp","url":"https://www.npmjs.com/package/@sigmacomputing/slack-mcp-server","page_url":"https://unfragile.ai/npm-sigmacomputingslack-mcp-server","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-sigmacomputingslack-mcp-server__cap_0","uri":"capability://tool.use.integration.slack.message.sending.via.mcp.protocol","name":"slack message sending via mcp protocol","description":"Enables LLM agents and tools to send messages to Slack channels and direct messages through the Model Context Protocol (MCP) transport layer. Implements MCP resource and tool schemas that map Slack API message endpoints to standardized function-calling interfaces, allowing Claude and other MCP-compatible LLMs to compose and dispatch messages without direct API credential handling.","intents":["Send notifications from an AI agent to a Slack channel when a task completes","Have an LLM compose and post formatted messages to Slack as part of a multi-step workflow","Enable Claude to notify team members via Slack without exposing API keys to the LLM context"],"best_for":["Teams building AI agents that need to notify Slack channels","Developers integrating Claude with Slack workflows via MCP","Organizations using Slack as a notification hub for AI-driven processes"],"limitations":["Message formatting limited to Slack's Block Kit and markdown syntax — no custom rendering","No built-in rate limiting or retry logic — relies on upstream MCP client for backpressure","Cannot send messages to private channels without explicit bot permissions configured in Slack workspace"],"requires":["Slack workspace with bot token (xoxb-*) with chat:write scope","MCP client implementation (e.g., Claude Desktop, custom MCP runner)","Node.js 18+ runtime for the MCP server process"],"input_types":["text (message content)","structured JSON (Slack Block Kit blocks)","channel ID or user ID (string)"],"output_types":["JSON response with message timestamp and channel confirmation","error object with Slack API error code if delivery fails"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-sigmacomputingslack-mcp-server__cap_1","uri":"capability://memory.knowledge.slack.channel.and.conversation.retrieval.via.mcp.resources","name":"slack channel and conversation retrieval via mcp resources","description":"Exposes Slack channels, conversation history, and metadata as MCP resources that LLM agents can query and reference. Implements MCP resource URIs (e.g., slack://channel/C123) that map to Slack API list and history endpoints, enabling agents to discover channels, read recent messages, and extract context without manual API orchestration.","intents":["Have an AI agent search for and read recent messages in a Slack channel to understand context","Retrieve a list of all channels in a workspace so an agent can decide which channel to post to","Extract conversation history from a thread to use as context for generating a summary or response"],"best_for":["AI agents that need to read Slack context before taking actions","Teams building Slack-aware assistants that reference recent conversations","Workflows where an LLM must discover channels dynamically based on workspace state"],"limitations":["Message history retrieval limited by Slack API pagination — typically 100 messages per request, requiring multiple calls for deep history","No real-time subscription to channel updates — agent sees snapshot at query time, not live changes","Private channel access depends on bot scopes (channels:read, groups:read) — cannot list or read channels the bot is not a member of"],"requires":["Slack bot token with channels:read, groups:read, and chat:history scopes","MCP client that supports resource URI dereferencing","Node.js 18+ for the MCP server"],"input_types":["channel ID (string, e.g., C123ABC)","channel name (string, e.g., #general)","optional limit parameter (integer) for message count"],"output_types":["JSON array of channel objects with metadata (name, topic, member count)","JSON array of message objects with user, timestamp, and text fields","error response if channel is not accessible or does not exist"],"categories":["memory-knowledge","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-sigmacomputingslack-mcp-server__cap_2","uri":"capability://data.processing.analysis.slack.user.and.workspace.metadata.lookup","name":"slack user and workspace metadata lookup","description":"Provides MCP tools to query Slack workspace users, their profiles, and workspace metadata (name, plan, member count). Implements calls to Slack's users.list, users.info, and team.info endpoints wrapped as MCP function tools, enabling agents to resolve user mentions, check user status, and understand workspace context without direct API calls.","intents":["Look up a user's email or profile information to mention them in a message","Check if a user is active or away before deciding whether to notify them","Retrieve workspace metadata to understand team size or plan tier for conditional logic"],"best_for":["Agents that need to resolve user identities or check availability before messaging","Workflows that customize behavior based on workspace metadata or user status","Teams building Slack bots that reference user profiles or workspace context"],"limitations":["User status (active/away) is cached by Slack and may be stale by seconds to minutes","Profile fields are limited to what the workspace admin has configured — custom fields may not be present","Cannot retrieve user email without users:read scope, which requires workspace admin approval"],"requires":["Slack bot token with users:read and team:read scopes","MCP client supporting function tool invocation","Node.js 18+"],"input_types":["user ID (string, e.g., U123ABC)","optional user email (string) for lookup","optional limit parameter for user list pagination"],"output_types":["JSON user object with id, name, email, real_name, profile fields, is_active, is_away","JSON workspace object with name, plan, member_count, created timestamp","error response if user not found or insufficient permissions"],"categories":["data-processing-analysis","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-sigmacomputingslack-mcp-server__cap_3","uri":"capability://tool.use.integration.slack.reaction.and.emoji.interaction","name":"slack reaction and emoji interaction","description":"Enables LLM agents to add, remove, and list emoji reactions on Slack messages through MCP tools. Wraps Slack's reactions.add, reactions.remove, and reactions.get endpoints as typed function calls, allowing agents to express sentiment, acknowledge messages, or trigger workflows based on emoji reactions without direct API credential exposure.","intents":["Have an agent add a checkmark emoji to a message to indicate task completion","Remove a reaction from a message if a condition changes","Check what reactions a message has received to gauge team sentiment or engagement"],"best_for":["Agents that use emoji reactions as lightweight workflow signals or acknowledgments","Teams building interactive Slack bots that respond to or manage reactions","Workflows where emoji reactions serve as status indicators or voting mechanisms"],"limitations":["Can only add reactions to messages the bot has visibility of — cannot retroactively react to old messages outside bot's history window","Emoji name must match Slack's internal emoji namespace — custom emoji names must be looked up separately","No bulk reaction operations — each reaction requires a separate API call, making mass reactions slow"],"requires":["Slack bot token with reactions:write and reactions:read scopes","Message timestamp and channel ID to target the message","MCP client supporting function tool invocation","Node.js 18+"],"input_types":["channel ID (string)","message timestamp (string, e.g., 1234567890.123456)","emoji name (string, e.g., 'thumbsup', 'checkmark')"],"output_types":["JSON confirmation object with ok: true and reaction name","JSON array of reaction objects with emoji name and user count","error response if message not found or emoji invalid"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-sigmacomputingslack-mcp-server__cap_4","uri":"capability://tool.use.integration.slack.thread.and.reply.management","name":"slack thread and reply management","description":"Allows LLM agents to post replies to message threads and retrieve thread context through MCP tools. Implements thread_ts parameter handling in message send operations and thread history retrieval, enabling agents to participate in conversations, maintain threaded discussions, and read full thread context without breaking conversation flow.","intents":["Post a reply to a specific message thread rather than the channel","Retrieve all messages in a thread to understand the full conversation context","Have an agent participate in a threaded discussion by reading and responding to thread messages"],"best_for":["Agents that need to maintain threaded conversations and avoid cluttering channels","Teams using threads for organized discussions and wanting AI participation","Workflows where an agent must read thread context before responding"],"limitations":["Thread replies are only visible when expanding the thread — not visible in channel view, limiting discoverability","Cannot create a new thread from scratch — must reply to an existing message to start a thread","Thread history retrieval limited by Slack API pagination — deep threads require multiple API calls"],"requires":["Slack bot token with chat:write and chat:history scopes","Parent message timestamp (thread_ts) to identify the thread","MCP client supporting function tool invocation","Node.js 18+"],"input_types":["channel ID (string)","thread timestamp (string, e.g., 1234567890.123456)","reply message text (string)","optional limit parameter for thread message count"],"output_types":["JSON message object with timestamp and thread_ts confirmation","JSON array of message objects in the thread with full context","error response if thread not found or message cannot be posted"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-sigmacomputingslack-mcp-server__cap_5","uri":"capability://tool.use.integration.mcp.server.lifecycle.and.configuration.management","name":"mcp server lifecycle and configuration management","description":"Implements the MCP server initialization, configuration, and transport layer for Slack integration. Handles stdio-based MCP protocol communication, tool and resource schema registration, and Slack API credential management through environment variables or configuration files. Manages the server lifecycle from startup through request handling and graceful shutdown.","intents":["Deploy an MCP server that Claude Desktop or other MCP clients can discover and connect to","Configure Slack API credentials securely without exposing them in prompts or client code","Register Slack tools and resources with proper MCP schemas so clients understand available operations"],"best_for":["Developers deploying Slack integration as a standalone MCP server","Teams using Claude Desktop or custom MCP runners that need Slack connectivity","Organizations that want to centralize Slack API access through a single MCP server instance"],"limitations":["Stdio-based transport limits to single client connection per server instance — requires multiple server instances for concurrent clients","Credential management relies on environment variables — no built-in secret rotation or vault integration","No built-in logging or observability — debugging requires manual instrumentation or external logging setup"],"requires":["Node.js 18+ runtime","Slack bot token provided via SLACK_BOT_TOKEN environment variable","MCP client implementation (Claude Desktop, custom runner, etc.)","npm or yarn for dependency installation"],"input_types":["environment variables (SLACK_BOT_TOKEN)","MCP protocol messages (JSON-RPC over stdio)"],"output_types":["MCP protocol responses (JSON-RPC over stdio)","tool and resource schema definitions (JSON)","server initialization confirmation"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":33,"verified":false,"data_access_risk":"high","permissions":["Slack workspace with bot token (xoxb-*) with chat:write scope","MCP client implementation (e.g., Claude Desktop, custom MCP runner)","Node.js 18+ runtime for the MCP server process","Slack bot token with channels:read, groups:read, and chat:history scopes","MCP client that supports resource URI dereferencing","Node.js 18+ for the MCP server","Slack bot token with users:read and team:read scopes","MCP client supporting function tool invocation","Node.js 18+","Slack bot token with reactions:write and reactions:read scopes"],"failure_modes":["Message formatting limited to Slack's Block Kit and markdown syntax — no custom rendering","No built-in rate limiting or retry logic — relies on upstream MCP client for backpressure","Cannot send messages to private channels without explicit bot permissions configured in Slack workspace","Message history retrieval limited by Slack API pagination — typically 100 messages per request, requiring multiple calls for deep history","No real-time subscription to channel updates — agent sees snapshot at query time, not live changes","Private channel access depends on bot scopes (channels:read, groups:read) — cannot list or read channels the bot is not a member of","User status (active/away) is cached by Slack and may be stale by seconds to minutes","Profile fields are limited to what the workspace admin has configured — custom fields may not be present","Cannot retrieve user email without users:read scope, which requires workspace admin approval","Can only add reactions to messages the bot has visibility of — cannot retroactively react to old messages outside bot's history window","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.41687235171028103,"quality":0.22,"ecosystem":0.3,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:24.482Z","last_scraped_at":"2026-05-03T14:23:32.814Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":6072,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-sigmacomputingslack-mcp-server","compare_url":"https://unfragile.ai/compare?artifact=npm-sigmacomputingslack-mcp-server"}},"signature":"R2T00mvhvEvI5oo8kyj3TChiXsUPEo/9tCjcqoS92JjJo1ZqRv/SHRLW48coFHGOIFpMwELyeTj3a27H+u8rCw==","signedAt":"2026-06-20T22:43:52.385Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-sigmacomputingslack-mcp-server","artifact":"https://unfragile.ai/npm-sigmacomputingslack-mcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=npm-sigmacomputingslack-mcp-server","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}