Hosted MCP server/Marketing

Plainrouter MCP server

Hosted at plainrouter.com·Streamable HTTP

Plainrouter connects an agent to Meta advertising work through one MCP endpoint at https://plainrouter.com/mcp. Clients sign in with OAuth or use a workspace key; new keys authorise a fixed set of selected workspaces with role-capped Read or Write access, and calls act on one workspace and one selected Meta ad account at a time. The documented path starts with a Read key for the first workspace check, then connecting Meta. The provider's setup guide covers Codex, Claude, Cursor, Gemini CLI, Grok, Muse, Hermes, OpenClaw, n8n and Make.

plainrouter.com Streamable HTTP OAuth or workspace key (role-capped Read or Write) Source checked Nov 12, 2026 Server responded when checked Reviewed 2026-11-16
About

Where it fits

Media buyers and agencies that want an agent to inspect and act on Meta ad accounts under workspace permissions.

  • Check workspace signal health.
  • Read an approved Meta ad account.
  • Submit a governed change proposal for approval.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds Plainrouter as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http plainrouter https://plainrouter.com/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://plainrouter.com/mcp
Host
plainrouter.com · /mcp
Transport
Streamable HTTP
Authentication
OAuth or workspace key (role-capped Read or Write)
Server name
plainrouter
Listing type
Community or directory listing

The installer uses the server name plainrouter. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that plainrouter appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Check workspace signal health. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server responded when checked

We reached plainrouter.com when we checked. That only means the address answered; it does not prove the MCP connection, sign-in, or tools work. The provider page was available when we checked.

Provider page available on Nov 12, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Plainrouter documentationhttps://plainrouter.com/docs/mcp/setupGitHub repositoryhttps://github.com/laravel/mcp/blob/cfa4f38f82873eeb6848527883545f98f871e229/UPGRADE.md