Skip to main content
Glama
Sign In
infralayers

pumble-mcp

Official
by infralayers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to pumble-mcp

No user-submitted related servers found.

    Related Servers

    • plutio-mcp

      thecreativelabs
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude and other MCP clients to interact with Plutio's business platform resources including CRM, projects, invoicing, and more through structured tools.
      44 npm
      5
      MIT

    • Slack Note Capture MCP Server

      larrygmaguire-hash
      F
      license
      A
      quality
      Not graded
      maintenance
      Enables two-way communication between Claude and Slack for posting messages, managing threads, and handling files. It specifically supports asynchronous workflows by allowing Claude to poll for remote user replies and send task notifications.
      9
      -

    • freedcamp

      cubo3
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects Claude to a project-management account so it can list and manage projects, tasks, comments, and files through eight REST API tools, including creating and updating tasks and adding comments.
      MIT

    • iOffice MCP

      chrischall
      A
      license
      A
      quality
      A
      maintenance
      Enables Claude clients to read and modify workplace and facilities management data through a REST API, with every write and state-changing tool gated behind a user confirmation prompt or a single-use confirmation token.
      53
      229 npm
      1
      MIT

    • Discord MCP Server

      swarit-soni
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with Discord through the REST API, supporting message reading and sending, channel and guild management, threads, pins, and reactions.
      17
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 26 tools

    Disambiguation4/5

    Tools mostly target distinct resource+action pairs (send vs reply vs schedule vs edit vs delete message, channel vs DM vs group DM, reactions, threads). Some names awkwardly embed usage guidance (list_channels_only_when_user_calls, list_users_not_for_id_lookup), but this actually reduces misselection. Minor overlap between send_message_via_channel_name_or_id and send_dm/send_group_dm, but descriptions clarify.

    Naming Consistency3/5

    Most tools follow verb_noun but with inconsistent long suffixes (via_channel_name_or_id, via_name_email_or_id, via_names_emails_or_ids, via_name_or_id), while others (edit_message, delete_message, add_reaction) drop the suffix entirely. Two tools embed conditional instructions in the name (only_when_user_calls, not_for_id_lookup), breaking the pattern. Still readable but mixed conventions.

    Tool Count3/5

    At 26 tools it sits just over the heavy threshold, and the surface spans messages, channels, DMs, threads, reactions, scheduled messages, users, groups, and status. Each tool does map to a distinct operation, but the set feels large and could be consolidated (e.g. the via_name_or_id variants).

    Completeness4/5

    Strong coverage of the chat domain: full message lifecycle, threads, reactions, DMs/group DMs, channel create and membership management, and complete scheduled-message CRUD. Gaps remain (no channel delete/archive/update, no file/attachment handling, user groups are list-only), but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources