Skip to main content
Glama
Dipeshpal

Capes

by Dipeshpal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Capes

No user-submitted related servers found.

    Related Servers

    • MailNet MCP Server

      Astroa7m
      F
      license
      Not graded
      quality
      B
      maintenance
      Unified email orchestration server for Gmail and Outlook with agentic tools for sending, reading, searching, and managing emails, enabling assistant-driven email workflows.
      2
      -

    • lenovmail

      satuapps
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to securely read, search, and send email across IMAP and Microsoft Graph accounts, with scoped tokens, approval flows, and an audit trail.
      1
      MIT

    • gmail-mcp

      Bloody-Regina
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage Gmail accounts, including searching, reading, sending, replying, forwarding, attachments, labels, and drafts across multiple mailboxes on a self-hosted Cloudflare Worker.
      MIT

    • Gmail MCP Server

      Abhitkumar89
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that lets AI assistants send, read, and manage Gmail through natural language, including email sending, inbox management, and template-based outreach.
      111 npm
      MIT

    • gmail-mcp

      hernandezhorace-ctrl
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search, read, send, reply, forward, and organize Gmail messages and threads across multiple Google accounts via a self-hosted Cloudflare Worker.
      146 npm
      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.3/5.0

    Scored across 62 tools

    Disambiguation4/5

    Tools are mostly cleanly separated by service and resource+action, e.g. Discord message/channel/role operations and Gmail message/draft/label operations. A few boundaries blur—discord_edit_channel/delete_channel also handle threads while thread creation is separate, and gmail_modify overlaps with trash/spam/archive—but descriptions clearly differentiate them.

    Naming Consistency4/5

    Strong service_action naming with snake_case throughout (discord_*, gmail_*, twitter_search). Most names follow verb_noun, but a handful are noun-only or vague (discord_member_role, discord_thread_member, gmail_modify, gmail_trash), which is a minor deviation rather than chaos.

    Tool Count1/5

    62 tools is far beyond the 3–15 well-scoped range and sits in the rubric's 50+ extreme-mismatch band. Even split across Discord, Gmail, and Twitter, the surface is very large and likely to burden tool selection.

    Completeness4/5

    Discord coverage is deep across messages, channels, roles, members, threads, invites, webhooks, moderation, and audit logs; Gmail covers search, read, send, reply, forward, labels, drafts, and message state. Minor gaps remain (e.g., Twitter is search-only, and there is no direct Discord message search or Gmail draft retrieval), but core lifecycle workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources