Skip to content
Plainrouter logo

Plainrouter MCP server

Which servers in the official MCP registry are Plainrouter's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-14

← Back to Plainrouter

Whose server it is
  • Registry namecom.plainrouter/mcpverified in the MCP registry

The registry name sits under plainrouter.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-14
  • Stateanswerschecked 2026-10-14
  • Tools15
  • Server calls itselfPlainrouter
  • Server version0.4.1
  • Protocol version2025-06-18

On 2026-10-14 the server answered initialize and tools/list without a sign-in. First answer in 382 ms.

Tools it offers15 tools · read 2026-10-14
  • get_account_state

    Return the authorized advertising account, workspace, connection, Signal destination, and currently available account capabilities. This read-only inspection tool does not change the account.

  • get_account_inventory

    Read the authorized workspace account inventory from the Meta mirror, with optional level, status, parent, and ID cursor filters.

  • list_workspaces

    List the workspaces and effective access tiers in this credential scope.

  • get_signal_health

    Diagnostic view of first-party event flow, Meta delivery outcomes, match quality, and reconciliation gaps from Plainrouter stored measurements. Not admissible evidence for spend-affecting proposals. Does not call the Marketing API.

  • get_performance

    Admissible proposal evidence: reconciliation meta_reported is the existing Meta-reported conversions count compared with gateway_verified accepted conversions. The separate purchases block shows Meta-reported Purchase counts under the…

  • get_inventory_metrics

    Read daily Meta metrics beside counted PlainRouter arrivals for mirrored campaigns, ad sets and ads. object_metrics contains account-timezone daily comparisons; unmatched_arrivals is one workspace/window count without unknown IDs. Counts…

  • verify_signal_ingestion

    Verify server-side Signal ingestion by writing one idempotent, identity-free modeled event for the authorized workspace. This confirms ledger receipt but does not count as real arrival evidence or complete onboarding. No spend capability.

  • propose-actions

    Propose a batch of budget, status, upload, or creative-duplication actions for the approved ad account. In Ask, every policy-allowed change waits for a person to approve it. In Full, policy-allowed changes run automatically. Rule…

  • dry_run_actions

    Preview policy decisions and execution diffs for a proposed Action batch without writing it.

  • list_actions

    List proposed actions for the authorized workspace and advertising account.

  • get_action_batch

    Get a proposed action batch for the authorized workspace and advertising account. Each action’s counted_evidence contains frozen proposal-time target figures and coverage; null means not captured.

  • get_action

    Get one proposed action for the authorized workspace and advertising account. counted_evidence contains frozen target figures and coverage captured at proposal time; null means not captured. The figures inform and never gate.

  • get_action_decision_receipt

    Get the persisted decision receipt for an authorized proposed action. Version 3 receipts include counted_evidence frozen at proposal time with account-currency values, coverage and the other-currency exclusion. Existing receipts are…

  • get_action_policy

    Get the effective Actions policy for the authorized workspace without creating a policy row.

  • actions.rules.list

    List stored performance rules available to this workspace key. This does not evaluate them.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "plainrouter": {
      "type": "http",
      "url": "https://plainrouter.com/mcp"
    }
  }
}

OpenAPI spec

35 paths, read 2026-10-14. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.