Skip to main content
Glama
thenavidm

Circle MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Circle MCP Server

No user-submitted related servers found.

    Related Servers

    • Circle MCP Server

      AnantBisht07
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Circle.so communities through Google OAuth 2.0, providing 20+ tools for comprehensive community management.
      5 npm
      MIT

    • Omnicord - Discord server

      OrygnsCode
      A
      license
      B
      quality
      A
      maintenance
      Gives your AI assistant full control of a Discord server: 148 tools for chat, moderation, automod, events, and administration, up to building a complete community server from one paragraph. Every destructive action previews first and waits for your confirmation.
      155
      273 npm
      9
      Elastic 2.0

    • intercom-mcp-server

      OtakuXavier
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Intercom's customer communications platform via the Intercom REST API, providing 102 tools for managing admins, articles, companies, contacts, conversations, and more.
      2
      MIT

    • Guild MCP

      Neural-Agent-Ledger
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes 59 tools that let MCP-compatible AI agents read and write to a public, typed social knowledge graph — creating and linking posts, leaving threaded comments, reacting, searching, managing sub-communities, and building reputation under an authenticated identity. Reading is free and writes spend the caller's credits, with all untrusted content spotlighted against prompt injection.
      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

    C2.6/5.0

    Scored across 170 tools

    Disambiguation3/5

    Many tools map to distinct resources, but the member-management surface is crowded with overlapping actions (create_member, create_lead, remove_member, delete_community_member, ban_community_member), and post tools (create_post, create_image_post, get_post, get_post_summary) require careful reading. With 170 tools, several boundaries are ambiguous enough that an agent could easily misselect.

    Naming Consistency4/5

    The set overwhelmingly follows a predictable snake_case verb_noun pattern (list_*, get_*, create_*, update_*, delete_*). Minor deviations like send_message, add_space_member, remove_space_member, tag_member, and untag_member are still readable and resource-specific.

    Tool Count1/5

    170 tools is an extreme mismatch for a coherent MCP surface, far beyond the recommended 3-15 range and even beyond the 50+ threshold that indicates poor scoping. The sheer volume overwhelms discovery and selection.

    Completeness2/5

    The domain is broad, but obvious lifecycle gaps exist: no create_workflow or update_workflow, no create_paywall, no update_image_post, and live rooms/transcripts are read-only. These missing operations would cause agent dead ends despite the large tool count.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources