Slack Max API MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SLACK_TOKEN | No | General Slack token fallback if bot or user tokens are not provided. | |
| SLACK_PROFILE | No | Specific active OAuth profile to use from the local token store. | |
| SLACK_BOT_TOKEN | No | Slack Bot User OAuth Token (xoxb-...) for manual token mode. | |
| SLACK_CLIENT_ID | No | Slack App Client ID for OAuth flows. | |
| SLACK_USER_TOKEN | No | Slack User OAuth Token (xoxp-...) for manual token mode. | |
| SLACK_CLIENT_SECRET | No | Slack App Client Secret for OAuth flows. | |
| SLACK_AUDIT_LOG_PATH | No | Path to the local audit log file. | ~/.slack-max-api-mcp/audit.log |
| SLACK_METHOD_DENYLIST | No | Comma-separated list of denied Slack API methods. | |
| SLACK_ENABLE_AUDIT_LOG | No | Enables or disables local JSONL audit logging. | true |
| SLACK_MAX_METHOD_TOOLS | No | The maximum number of Slack method tools to expose. | |
| SLACK_METHOD_ALLOWLIST | No | Comma-separated list of allowed Slack API methods (e.g., chat.postMessage,conversations.history). | |
| SLACK_ONBOARD_SERVER_URL | No | Override URL for the central onboarding server used during team member onboarding. | |
| SLACK_TOOL_EXPOSURE_MODE | No | Sets the tool exposure mode: operations (default, 21 operations-first tools), developer (operations + gateway + core tools), or legacy (fixed core tools + optional catalog tools). 'smart' is an alias for 'developer'. | |
| SLACK_ENABLE_METHOD_TOOLS | No | Enables or disables fixed core Slack API method tools (true|false). | |
| SLACK_METHOD_DENY_PREFIXES | No | Comma-separated list of denied Slack API method prefixes (e.g., admin.). | |
| SLACK_METHOD_ALLOW_PREFIXES | No | Comma-separated list of allowed Slack API method prefixes (e.g., chat.,conversations.). | |
| SLACK_OPERATIONS_STATE_PATH | No | Override path for the local operations state file. | ~/.slack-max-api-mcp/operations-state.json |
| SLACK_OPERATIONS_CONFIG_PATH | No | Override path for the operations config file (defaults to config/operations.json). | |
| SLACK_SMART_COMPAT_CORE_TOOLS | No | Enables or disables smart compatibility for core tools (true|false). | |
| SLACK_ALLOW_ENV_EXAMPLE_FALLBACK | No | Allows falling back to .env.example if no other tokens are found (true|false). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ops_policy_infoB | Show operational guardrails for this MCP (method policy and local audit settings). |
| ops_access_policy_infoB | Show access-control profiles, effective rules, pending elevation requests, and active grants. |
| ops_access_policy_setC | Switch the active Slack access-control profile for this MCP runtime state. |
| ops_access_requestA | Create a scoped Slack access elevation request that must be approved before it becomes active. |
| ops_access_approveA | Approve a pending access elevation request and convert it into an active time-boxed grant. |
| ops_access_revokeA | Revoke one active access grant, or all active grants, and persist the revocation in local state. |
| ops_recent_failuresC | List recent tool, Slack API, or access-control failures from local diagnostics state. |
| ops_explain_errorB | Explain a recorded failure in human-readable form using the latest diagnostics snapshot. |
| ops_playbook_listB | List built-in operations playbooks that can run multi-step Slack workflows. |
| ops_state_overviewC | Inspect local operations state for incidents, digests, broadcasts, followups, and playbook runs. |
| ops_incident_createC | Create and optionally announce a tracked incident record using config-backed incident templates. |
| ops_incident_updateC | Update a tracked incident, optionally post a thread update, and persist the new operational status. |
| ops_incident_closeB | Close a tracked incident, optionally post a closure update, and persist the final resolution. |
| ops_broadcast_prepareB | Create a tracked broadcast draft before sending it to one or more channels. |
| ops_playbook_runC | Run a named operations playbook (incident open, support digest, release broadcast) with config-backed defaults and state persistence. |
| ops_channel_snapshotC | Operational snapshot for a channel: activity volume, participants, threads, reactions, and recent samples. |
| ops_unanswered_threadsC | Find unanswered or stale question-like threads in a channel for follow-up operations. |
| ops_sla_breach_scanC | Scan multiple channels for threads that exceed an SLA threshold without external replies. |
| ops_sla_followupB | Post reminder replies to SLA-breached threads across channels (supports dry-run). |
| ops_broadcast_messageC | Broadcast the same operational message to multiple channels, or send a prepared broadcast draft. |
| ops_audit_log_readC | Read recent local audit log entries for governance and troubleshooting. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 21 tools
Most tools have distinct purposes within the Slack operations domain, but some overlap exists. For example, ops_access_policy_info and ops_policy_info both relate to policy information, which could cause confusion. However, descriptions clarify that the former focuses on access-control profiles while the latter covers operational guardrails, helping to differentiate them.
Tool names follow a highly consistent pattern throughout, using the 'ops_' prefix followed by a descriptive verb_noun structure (e.g., ops_access_approve, ops_incident_create). This uniformity makes the set predictable and easy to navigate, with no deviations in naming conventions.
With 21 tools, the count is borderline high for a focused operations server, potentially feeling heavy. While the tools cover various aspects like access control, incidents, broadcasts, and SLA management, some consolidation might improve usability without losing functionality.
The tool set provides comprehensive coverage for Slack operations, including CRUD-like lifecycle management for incidents (create, update, close), access control (request, approve, revoke), and monitoring (audit logs, failures, SLA breaches). No obvious gaps are present, ensuring agents can handle full workflows without dead ends.