Skip to main content
Use Plainrouter’s Model Context Protocol (MCP) server to read one Meta ad account and request creative changes for human approval. Start with synthetic data or connect your workspace.

Set up your connection

Configure Claude Code, try the sandbox, and verify the bound Meta ad account.

Explore the tools

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

​
What can I do with Plainrouter MCP?

Budget changes, ad activation, and delivery-status execution are unavailable. Suggest only records proposals and approvals without executing them.

​
How do I get started?

1

Connect a client

Use the sandbox without an account, or configure the production endpoint with a workspace execution token. Follow Setup.
2

Verify the account

Call get_account_state. In production, confirm the returned workspace and Meta ad account before requesting more data or a proposal.
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?

The setup guide includes Claude Code configuration. Other clients need remote HTTP MCP support and a way to send a fixed bearer credential. A client that requires OAuth sign-in for every remote server cannot use Plainrouter’s production token flow as documented here. 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 token.

​
Access and approval

A workspace owner issues the token for the intended Meta ad account. Start with the Read tier for account and creative-library inspection; proposal-producing tools require Write or Admin. Choose a token tier.
Plainrouter MCP uses workspace execution tokens. OAuth management credentials and Signals workspace 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, human approval, 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. For creative generation and other advertising workflows, see AI tools for Facebook ads.