{ "content": [ { "type": "text", "text": "{\n \"ok\": true,\n \"status\": 200,\n \"data\": { ... },\n \"context\": { ... }\n}" } ] } ``` - Error shape (encoded in content[0].text) includes: - ok: false - status: HTTP-like status code (for example 400, 401, 500) - error: message ### slack_query_suggestions - Classification: read-only, low risk. - Use when: - You want schema discovery and workflow recommendations for every other MCP tool. - Do not use when: - You only need known endpoint names (use slack_list_methods). - Permissions/prerequisites: - No authorizationKey required. - Parameters and constraints: - toolName: optional non-empty string; exact tool name filter. - query: optional non-empty string; simple text match against tool metadata. - includeExamples: optional boolean (default true). - includeAdmin: optional boolean (default true). - Expected data payload: - summary: filter metadata and counts. - recommendations: common usage sequences. - tools: per-tool guidance, parameter schema, and optional examples. - Recommended tools: - Follow-up: invoke any recommended tool sequence directly from response. - Example: ```json { "name": "slack_query_suggestions", "arguments": { "query": "history", "includeExamples": true } } ``` ### slack_connection_info - Classification: read-only, low risk. - Use when: - You need to verify server metadata, auth-gate configuration, effective request user, Slack client connection config, or token store wiring. - Do not use when: - You need to validate a specific Slack token's runtime permissions (use slack_auth_test). - Permissions/prerequisites: - No authorizationKey required. - Requires server startup with valid env parsing. - Parameters: - none. - Expected data payload: - server: name, version, adminAuthConfigured, scopeModel, requestUserId. - slack: service connection info. - tokenStore: token-store connection info or null. - Common failures: - Rare; usually process misconfiguration causing server startup failure before tool execution. - Recommended tools: - Prerequisite/companion: slack_scope_info. - Follow-up: slack_auth_test. - Example: ```json { "name": "slack_connection_info", "arguments": {} } ``` ### slack_scope_info - Classification: read-only, low risk. - Use when: - You need deterministic app/user scoping paths for Vault token index and Postgres config keys. - Do not use when: - You need actual token values or token metadata (use admin token tools). - Permissions/prerequisites: - No authorizationKey required. - Parameters: - userId: optional non-empty string. - If omitted, defaults to MCP_CONFIG_DEFAULT_USER_ID. - Expected data payload: - appName, userId, userIdPathSegment. - postgres model and vault tokenIndexPath. - Common failures: - Invalid empty userId. - Recommended tools: - Prerequisite: slack_connection_info. - Follow-up: slack_admin_token_set. - Example: ```json { "name": "slack_scope_info", "arguments": { "userId": "alice" } } ``` ### slack_list_methods - Classification: read-only, low risk. - Use when: - You want a discoverable list of Slack wrapper endpoints available from this MCP service. - Do not use when: - You already know the target method and need execution (use specific tool or slack_api_call). - Permissions/prerequisites: - No authorizationKey required. - Parameters: - none. - Expected data payload: - endpoints: list of known wrapper method descriptors. - Common failures: - None typical beyond runtime service-client initialization issues. - Recommended tools: - Follow-up: slack_api_call or dedicated wrapper tools. - Example: ```json { "name": "slack_list_methods", "arguments": {} } ``` ### slack_auth_test - Classification: read-only, low risk. - Use when: - You need to validate token identity/workspace and confirm user-token routing is working. - Do not use when: - You need channel/message data. - Permissions/prerequisites: - No authorizationKey required. - Token must exist for resolved user (token store or fallback env token). - Parameters: - tokenUserId: optional non-empty string. - Expected data payload: - data: Slack auth.test response. - context: tokenUserId and tokenSource used for this invocation. - Common failures: - 400 no Slack token configured for resolved user. - 500 missing SLACK_BOT_TOKEN when token store is absent. - Slack API errors (invalid_auth, account_inactive, etc.). - Recommended tools: - Prerequisite: slack_connection_info. - Follow-up: slack_conversations_list. - Example: ```json { "name": "slack_auth_test", "arguments": { "tokenUserId": "alice" } } ``` ### slack_conversations_list - Classification: read-only, moderate risk (can expose workspace metadata). - Use when: - You need channels/DM containers and pagination cursors. - Do not use when: - You need message bodies (use slack_conversation_history). - Permissions/prerequisites: - No authorizationKey required. - Token needs conversation-list scopes (for example channels:read/groups:read/im:read/mpim:read). - Parameters and constraints: - types: optional non-empty string (Slack conversations.list types format). - excludeArchived: optional boolean. - limit: optional positive int <= 999. - cursor: optional non-empty string. - teamId: optional non-empty string. - tokenUserId: optional non-empty string. - Expected data payload: - Raw Slack conversations.list response in data. - context includes tokenUserId/tokenSource. - Common failures: - 400 invalid parameter shapes. - Slack missing_scope/not_in_channel-like access failures. - Recommended tools: - Prerequisite: slack_auth_test. - Follow-up: slack_conversation_history. - Example: ```json { "name": "slack_conversations_list", "arguments": { "types": "public_channel,private_channel", "excludeArchived": true, "limit": 100, "tokenUserId": "alice" } } ``` ### slack_conversation_history - Classification: read-only, moderate risk (message-content access). - Use when: - You need messages from one conversation with cursor/time-window filtering. - Do not use when: - You only need channel discovery (use slack_conversations_list). - Permissions/prerequisites: - No authorizationKey required. - Token needs history scopes for the target conversation type. - Parameters and constraints: - channel: required non-empty string. - cursor: optional non-empty string. - limit: optional positive int <= 999. - oldest/latest: optional non-empty string (Slack timestamp string). - inclusive/includeAllMetadata: optional booleans. - tokenUserId: optional non-empty string. - Expected data payload: - Raw Slack conversations.history response in data. - context includes tokenUserId/tokenSource. - Common failures: - 400 missing channel. - Slack channel_not_found, not_in_channel, missing_scope. - Recommended tools: - Prerequisite: slack_conversations_list. - Follow-up: slack_user_info (to resolve user ids in messages). - Example: ```json { "name": "slack_conversation_history", "arguments": { "channel": "C0123456789", "limit": 50, "oldest": "1710000000.000000", "tokenUserId": "alice" } } ``` ### slack_user_info - Classification: read-only, moderate risk (PII exposure depending on scopes). - Use when: - You need profile details for a Slack user id. - Do not use when: - You need to list users in bulk (use slack_api_call with users.list if needed). - Permissions/prerequisites: - No authorizationKey required. - users:read scope required; users:read.email for email fields. - Parameters and constraints: - user: required non-empty string. - includeLocale: optional boolean. - tokenUserId: optional non-empty string. - Expected data payload: - Raw Slack users.info response in data. - context includes tokenUserId/tokenSource. - Common failures: - 400 missing user. - Slack user_not_found or missing_scope. - Recommended tools: - Prerequisite: slack_auth_test. - Follow-up: slack_post_message (for user-related workflows). - Example: ```json { "name": "slack_user_info", "arguments": { "user": "U0123456789", "includeLocale": true, "tokenUserId": "alice" } } ``` ### slack_post_message - Classification: mutating, high risk. - Use when: - You need to send a message to a channel/DM/thread. - Do not use when: - You need read-only checks (use auth/list/history tools). - Permissions/prerequisites: - chat:write scope required. - If MCP_ADMIN_AUTH_KEY is set, authorizationKey is required and must match. - Parameters and constraints: - channel: required non-empty string. - text: optional string, 1..40000 chars when provided. - blocks: optional array

slack-mcp

Installation