Skip to main content
Glama
Sign In
KamyarTaher

@attrkit/mcp

by KamyarTaher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @attrkit/mcp

No user-submitted related servers found.

    Related Servers

    • Meta Ads MCP Server

      masato89994
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables managing Meta advertising accounts, campaigns, ad sets, creatives, audiences, reporting, and batch workflows through an authenticated MCP endpoint with per-workspace OAuth connections.
      10 npm
      MIT
    • @prompteden/mcp-server by yulanventures

      @prompteden/mcp-serverofficial

      yulanventures
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients such as Claude, Codex, and Cursor to read projects, monitors, captured AI answers, account/plan usage, and AI-referral analytics, and to set up projects, monitors, goals, and analytics properties. It also supports checking tracking-snippet verification, with monitor creation starting metered runs that consume credits.
      20
      43 npm
      MIT

    • Meta Ads MCP Server

      Ana1729
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables account setup, campaign/ad set/creative/audience management, reporting insights, and batch workflows against the Meta Marketing API, with OAuth-backed multi-tenant workspace authentication.
      10 npm
      MIT

    • mailly-mcp

      superagents-lab
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables authenticated management of email, drafts, sending, domains, contacts, templates, campaigns, workflows, and webhooks through typed MCP tools backed by a REST API.
      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.1/5.0

    Scored across 39 tools

    Disambiguation4/5

    Most tools are clearly separated by resource and action (apps, API keys, integrations, links, spend, events, webhooks), and the descriptions add useful distinguishing detail. A few analytics tools overlap: list_campaigns exposes recommendation/profit fields also surfaced by get_campaign_decision, and list_ads/get_spend both touch performance and spend, so agents may need to read descriptions carefully.

    Naming Consistency4/5

    Names are overwhelmingly lowercase snake_case with a verb_noun pattern (list_apps, create_integration, update_link_status), making the set predictable. Exceptions like whoami and minor verb choices such as archive versus delete or get versus lookup are still readable and semantically reasonable.

    Tool Count2/5

    39 tools is well above the 3-15 well-scoped range and makes this a heavy MCP surface. Although the platform is broad, the tool count likely needs splitting or consolidation into more focused servers.

    Completeness4/5

    Coverage spans app lifecycle, API keys, integrations, links, campaigns/decisions, spend, events, webhooks, RevenueCat, and usage caps, so core workflows are mostly complete. Minor gaps remain: no app delete (archive only), no link delete, no webhook update, and no single-resource getters for some resources.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources