Skip to main content
Glama
hlee

FeedMob MCP Server

by hlee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to FeedMob MCP Server

No user-submitted related servers found.

    Related Servers

    • Fleet MCP

      SimplyMinimal
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Fleet Device Management for device management, security monitoring, and compliance enforcement through the Model Context Protocol.
      5
      MIT
    • Fireblocks MCP Server by fireblocks

      Fireblocks MCP Serverofficial

      fireblocks
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to securely interact with Fireblocks services through the Model Context Protocol, supporting transaction management, vault and exchange account queries, network connections, and workspace user management.
      16 npm
      10
      MIT
    • @vitrion/zentria-mcp by vitrionbv

      @vitrion/zentria-mcpofficial

      vitrionbv
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to access and manage Zentria CRM data, including sales, customers, to-dos, and more, through the Model Context Protocol.
      80
      22 npm
      MIT
    • funnelkeeper-mcp by ae-labs-inc

      funnelkeeper-mcpofficial

      ae-labs-inc
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a Model Context Protocol interface to a growth and revenue API, enabling MCP clients to manage account data and interact with platform tools through natural-language-driven tool calls.
      3 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.4/5.0

    Scored across 18 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific resources (campaigns, clients, metrics, etc.) with no overlap. The 'get_' tools retrieve single entities by ID, while 'list_' tools return collections with filters, creating a clean separation. An agent can easily distinguish between tools like get_campaign and list_campaigns based on whether they need details or a filtered list.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with perfect uniformity. The 'get_' prefix is used for retrieving single entities, and 'list_' for collections, applied consistently across all resources (campaigns, clients, partners, etc.). This predictable naming makes it easy for agents to infer tool purposes and navigate the set.

    Tool Count4/5

    With 18 tools, the count is slightly high but reasonable for a comprehensive advertising/campaign management domain. It covers multiple resource types (campaigns, clients, partners, playbooks, etc.) with both detail and listing operations, avoiding bloat. A minor reduction might streamline it, but each tool earns its place by serving a distinct function.

    Completeness4/5

    The tool set provides strong coverage for a FeedMob advertising platform, including core CRUD-like operations (get and list) for key entities like campaigns, clients, and partners. Minor gaps exist, such as missing update/delete tools or campaign creation, but agents can work around these for read-heavy use cases. The inclusion of metrics, documents, and playbooks adds useful breadth.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources