Skip to main content
Glama
Sign In
mkt

mkt

by roy-tong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mkt

No user-submitted related servers found.

    Related Servers

    • approval-gated-mcp

      qcwebworks
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to read campaign and account data freely while routing every write through human-approved plans, with budget caps, drift refusal, undo, and audit logging.
      6
      MIT

    • google-ads-mcp

      adginr
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to manage Google Ads accounts through guarded tools for GAQL reporting, keywords, ads, budgets, callouts, and sitelinks, with dry runs and paused-by-default creates.
      Apache 2.0

    • ProdForge

      CloudCorpRecords
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to list fleet packages, generate merged MCP configs, run production checklists and doctor reports, inspect catalog health, and execute release ship gates. It provides a single MCP interface for connecting and validating the production toolchain.
      101 npm
      MIT

    • enterprise-agent-mcp

      lzyruc
      F
      license
      C
      quality
      C
      maintenance
      Enables stdio-capable MCP clients to run governed enterprise operations tasks, including policy/runbook retrieval and ticket and user lookups or writes. High-risk actions are held for human approval and role-based access is enforced server-side, so clients cannot bypass governance.
      4
      1
      -

    • branchlift

      MuratKomurcu1
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables local MCP access to attach to isolated backend environments, monitor runtime health/logs, check security posture, manage snapshots and diffs, audit events, and view sanitized remote inventory.
      11 npm
      Apache 2.0
    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

    C2.9/5.0

    Scored across 43 tools

    Disambiguation3/5

    Descriptions are unusually explicit about each tool's scope and negative space ("只读…不自动…"), which genuinely helps. However there is a dense cluster of near-synonymous planning/analysis views — mkt_goals vs mkt_goal_plan vs mkt_strategy vs mkt_channel_plan vs mkt_sprint_plan vs mkt_cadence vs mkt_gtm_design — and another of reporting views — mkt_status vs mkt_ledger_query vs mkt_scorecard vs mkt_result vs mkt_progress vs mkt_campaign — where an agent could easily pick the wrong one. mkt_memory vs mkt_experience vs mkt_playbooks is also hard to separate at selection time.

    Naming Consistency3/5

    All names share the mkt_ prefix and snake_case, so surface consistency is fine. But the stem mixes nouns (mkt_goals, mkt_strategy, mkt_deals, mkt_voice, mkt_inbox, mkt_journey) with verbs (mkt_search, mkt_optimize, mkt_revise, mkt_audit, mkt_orchestrate), so you cannot infer from the name whether a tool lists, computes, or mutates.

    Tool Count2/5

    43 tools is well past the heavy threshold for what is largely one marketing-ops workflow. Many planning/analysis views are narrow read-only lenses that could be consolidated into fewer parameterized tools.

    Completeness4/5

    The surface covers the full lifecycle: channel/capability registries, goal and plan design, lint/validation, gated execution (mkt_action, mkt_run_queue), measurement, retro, and learning/experience. The write side is intentionally thin (approval and first-run calibration live only in the human CLI), which is a defensible design but leaves no MCP path to author or approve plans.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources