Skip to main content
Glama

Related Servers

Alternatives to Slack Max API MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes Slack Web API operations as tools, enabling users to list conversations, read history, post messages, and call any Slack Web API method.
      32 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables interaction with Slack workspaces through tools for managing channels, sending messages, and retrieving user profiles. It leverages the Slack API and FastMCP to provide functionalities like message history lookup and reaction management.
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      A production-ready MCP server for the Slack API that enables searching, listing channels, reading history, inspecting users, fetching threads, and sending messages through controlled Slack tools.
      30,839 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      This MCP server provides integration with the Slack API via HTTP transport, allowing for channel management and message operations. It enables users to list channels, send or edit messages, search message history, and retrieve user information through standardized tools.
      32 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to search and retrieve messages within a Slack workspace using the Slack Web API. It supports specific channel filtering and includes built-in rate limit handling for efficient message discovery.
      32 npm
      MIT

    TDQS

    B3.2/5.0

    Scored across 21 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count3/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing