Skip to main content
Glama
CTMJSON

ctm-multi-mcp

Official
by CTMJSON
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ctm-multi-mcp

No user-submitted related servers found.

    Related Servers

    • meta-mcp

      nourpups
      A
      license
      C
      quality
      D
      maintenance
      Read-only MCP server for Meta (Facebook) Graph API, enabling access to Marketing API, Pages, Instagram, and WhatsApp Business data through Claude Code and any MCP-compatible client.
      30
      4 npm
      1
      MIT

    • Telegram Lead Analysis MCP

      zeropennyads
      F
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that exposes Telegram lead conversations to Claude for sales analysis, enabling lead summary, intent, stage, and follow-up insights.
      -

    • Google Ad Manager MCP

      Bizclik-Media
      F
      license
      A
      quality
      C
      maintenance
      Read-only MCP server that connects Claude Desktop to the publisher-side Ad Manager API so users can browse networks, saved reports, orders, and line items, and run saved reports to pull their rows into a conversation. No tool mutates data, and per-user OAuth ensures each person inherits only their existing account permissions.
      5
      -

    • google-ads-mcp-cloudflare

      phwtsp
      F
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server that connects Google Ads to Claude via Cloudflare Workers, supporting account/campaign/ad reports, keywords, search terms, and GAQL queries with OAuth 2.1 authentication.
      -
    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

    A4/5.0

    Scored across 32 tools

    Disambiguation4/5

    The list_*/get_* pairs are each clearly scoped to a distinct entity (numbers, contacts, sources, etc.). The reporting tools (call_disposition_report, call_summary_report, call_export, call_crosstab, reports_series) have overlapping call-data purposes but their descriptions clarify distinct output formats and use cases, so an agent can usually pick correctly.

    Naming Consistency4/5

    The dominant pattern is list_<entity> / get_<entity>, which is consistent and predictable. The reporting tools deviate with names like call_export, call_crosstab, and reports_series, which are still descriptive but don't follow a uniform verb_noun convention. Overall the set is orderly, not chaotic.

    Tool Count3/5

    At 32 tools, the server is on the heavy side, exceeding the 3-15 tool sweet spot. However, the count is largely justified by the need to cover 12+ entity types with list/get pairs plus several reporting tools. It's not bloated with redundant duplicates, but it does tax an agent's context window.

    Completeness4/5

    The server covers a wide range of call-tracking resources (calls, numbers, contacts, sources, queues, bots, menus, schedules, routes, users, tags, texts) and provides multiple reporting/export options. Minor gaps exist: no get_text, get_tag, or get_sub_account, and no mutation operations, but for a read-heavy reporting API this is largely complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources