Skip to main content
Use Plainrouter’s Model Context Protocol (MCP) server to inspect workspace Signals setup, compare arrivals, read an authorized Meta ad account, and request creative changes governed by Ask or Full. Start with an authenticated read from your workspace.

Set up your connection

Choose your client, configure authorization and verify workspace access.

Explore the tools

Check tool inputs, outputs, permissions, and side effects.

​
What can I do with Plainrouter MCP?

In Ask mode, a person approves every change first. In Full mode, admitted unprotected changes can run automatically; protected batches still need a person approval. Every change gets a receipt, and the kill switch stops all changes. Canonical pause, resume, increase_budget, and decrease_budget proposals follow the selected mode. Both modes apply current execution checks. New proposals and previews refuse set_status, adjust_budget, replace_creative, shift_spend, and rollback; stored historical actions of those types never execute. Use supported action types. Historical Suggest only batches record approvals without executing them. For repeatable Signals tasks, the server also supplies three built-in prompts: installation, claimed-versus-counted comparison, and signal health. They return instructions; the client still needs authorization to run the referenced tools. For a fair comparison, keep definitions beside the figures: arrivals cover all site channels, claimed clicks are Meta outbound clicks, journey credit uses observed touches, and Meta’s claimed purchases follow its own attribution rules. Read comparison limits. Plainrouter’s built-in creative generation and rendering have been retired. Uploaded creatives and governed proposals have separate workspace availability and permission requirements; discovery alone does not enable them.

​
How do I get started?

1

Connect a client

Create a Plainrouter account and configure the endpoint with a Workspace key or supported OAuth sign-in. Follow Setup.
2

Verify the account

For account-specific work, call get_account_state and confirm the returned workspace and Meta ad account. For workspace installation, call get_install_instructions and confirm its workspace; no Meta account is required.
3

Choose a workflow

Start with a read. Use Signals diagnostics, or follow the creative proposal walkthrough when you are ready to request a change.

​
Connection details

​
Which clients can connect?

Clients can authenticate with a workspace key sent as a bearer credential, or sign in with OAuth. OAuth sign-in asks you to choose the Meta ad account and Read or Write access. Follow Claude OAuth setup, or use Claude Code key configuration for scripted access. Custom clients should follow the protocol and header requirements. Plainrouter does not issue an Mcp-Session-Id; authenticate each production tool request with the workspace credential.

​
Connect ChatGPT

On a paid ChatGPT plan with developer mode:
  1. Enable developer mode and add https://plainrouter.com/mcp with OAuth.
  2. Sign in to Plainrouter and choose an active Meta ad account and Read or Write access.
  3. Verify an authenticated read and confirm the returned workspace and selected Meta ad account. The unauthenticated sandbox is retired.

​
Access and approval

A workspace owner or member creates a key within their current role under Settings → Workspace keys. Start with Read for account, creative-library and Actions record inspection. Previews and proposals require Write and their applicable grants. Older Read keys without read-actions need fresh authorization for those reads. Choose a token tier.
Plainrouter MCP accepts Workspace keys and workspace-scoped OAuth execution tokens from client sign-in. OAuth management credentials and Server secrets do not authenticate MCP tool calls.
Reads, diagnostics, and proposals have different effects. get_signal_health reads stored measurements; get-creative-library contacts Meta. The optional verify_signal_ingestion diagnostic writes an identity-free event and does not prove a real website arrival. Creative proposal calls write to Plainrouter; they do not directly create the Meta ad. Policy checks, the selected Ask/Full mode, and provider verification govern supported creative execution. A proposal or approval is not Landed. Review the tool reference for exact permissions and the proposal review guide for execution states.

​
Continue with your task

Still evaluating providers? Read the Meta Ads MCP comparison, or see the hosted Meta Ads MCP server overview for supported clients and pricing. Comparing Google connectors instead? See Google Ads MCP servers compared. For creative generation and other advertising workflows, see AI tools for Facebook ads.