Skip to main content
Glama
hamza-shamas

pressadvantage-mcp

by hamza-shamas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to pressadvantage-mcp

No user-submitted related servers found.

    Related Servers

    • @restforge-dev/mcp-server by restforge

      @restforge-dev/mcp-serverofficial

      restforge
      A
      license
      A
      quality
      C
      maintenance
      MCP server that exposes RESTForge capabilities to AI agents, enabling them to set up, configure, generate code, and manage RESTForge projects through natural language.
      29
      44 npm
      MIT

    • paperclip-mcp

      darljed
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the Paperclip AI agent orchestration API, enabling management of AI companies, agents, projects, and tasks through any MCP-compatible client.
      38 npm
      4
      MIT

    • vibe-agent-mcp

      yagaMI-Reverse
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the Vibe-Marketer Agent API that enables generating ads, auditing landing pages, and running local preflight checks on ad compliance, with an autonomous agent loop to improve results.
      -

    • wrapmcp

      SubZtep
      A
      license
      Not graded
      quality
      C
      maintenance
      Universal MCP server that wraps any CLI tool, enabling AI assistants to run commands via natural language.
      MIT

    • prism-mcp

      skyphusion-labs
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server providing full HTTP parity with the Prism API, enabling agents to chat, generate images/video/music/TTS, manage RAG documents and projects, and poll long jobs without a browser.
      2 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.2/5.0

    Scored across 37 tools

    Disambiguation4/5

    Most tools are clearly separated by resource and action, such as releases, scheduled orders, organizations, and pixels. Potential overlaps like create_release vs order_written_release are explicitly distinguished, and sandbox tools are clearly labeled as testing-only. The main challenge is the sheer number of options, but each has a distinct purpose.

    Naming Consistency3/5

    The naming pattern is mostly verb_noun (list_releases, create_organization, update_pixel), but there are notable deviations. For example, sandbox_editor_rejects and sandbox_editor_approves use a noun-verb structure while sandbox_approve_with_exception uses a verb-first structure, and add_first_release_keyword is a verbose variant of add_scheduled_keyword. This mixed style is still readable but not fully consistent.

    Tool Count2/5

    With 37 tools, the server has an excessive number for a single domain, exceeding the typical well-scoped range of 3-15 tools. The 5 sandbox simulation tools add bulk and are only for testing, further inflating the count. This makes the tool surface feel heavy and difficult for agents to navigate efficiently.

    Completeness4/5

    The toolset provides extensive coverage of press release management: full lifecycle for releases (create, get, approve, reject, revise, cancel, finalize), scheduled orders, organization management, pixels, distribution upgrades, and pickup URLs. Minor gaps include missing delete operations for scheduled orders and releases (though cancel exists), but the core workflows are solid.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources