Skip to main content
Glama
katekruger

campaign-preflight-mcp

by katekruger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to campaign-preflight-mcp

No user-submitted related servers found.

    Related Servers

    • Mailchimp MCP Server

      AgentX-ai
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides read-only access to Mailchimp's Marketing API for comprehensive email marketing data retrieval.
      38
      282 npm
      11
      MIT

    • mkt

      roy-tong
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to inspect operational status and channels, lint human-reviewed plans, search and query ledger data, and run queue-based writes with dry-run defaults and safeguards against unverified or unapproved campaigns.
      MIT

    • seshat-bi

      Kemetra
      A
      license
      A
      quality
      A
      maintenance
      A read-only MCP server that reports BI pipeline readiness, blockers, and the next allowed action for governed Power BI workflows. It never writes files, executes warehouse work, or grants human approvals.
      6
      178 npm
      60 PyPI
      2
      Apache 2.0

    • sentinel-recovery-services

      TerminallyLazy
      F
      license
      Not graded
      quality
      A
      maintenance
      Read-only MCP server that performs deterministic local preflights of agent-payment boundary documents and x402 v2 PaymentRequired JSON, and prepares unsubmitted public quote-request drafts without network calls or fund movement.
      -

    • willitsend

      abryfs
      A
      license
      A
      quality
      D
      maintenance
      A deterministic preflight checker for outbound SMS/iMessage that catches silent filtering, segment blowups, and dropped iMessage features before sending.
      1
      34 npm
      1
      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

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: three preflight runners for different input sources (demo, files, live), two for rule management (list and explain), and one for config validation. There is no overlap in their operations, and the descriptions make it obvious which to select.

    Naming Consistency4/5

    Names use a consistent 'preflight_' prefix across all tools, but the pattern is not fully uniform: the first three are verbs implied by the domain (e.g., 'preflight_demo' runs a demo), while the last three explicitly start with verbs ('list_', 'explain_', 'validate_'). This is a minor deviation that agents can easily adapt to.

    Tool Count5/5

    With six tools, the server is well-scoped and avoids unnecessary bloat. Each tool covers a distinct aspect of the preflight workflow—execution sources, rule catalog, and configuration—so the count feels appropriately sized for the domain.

    Completeness4/5

    The surface covers the core lifecycle: running preflights on demo, files, or a live Instantly campaign; inspecting and understanding rules; and validating config files. A minor gap is the lack of a tool to run preflight on a manually specified set of parameters or a generic input, but the provided sources handle common use cases adequately.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources