1. Create a workspace key
In Plainrouter, select your workspace and open Settings → Workspace keys. Create a Read key for analysis; use Write for Actions previews and proposals. A new Read key can also inspect Actions records and policy. Copy it once into your protected credential configuration. Select the intended workspace under Workspaces. A key can cover a fixed set of workspaces; for more than one, calllist_workspaces and pass workspace_id on later tool calls. Workspace selection. Never put keys in prompts or source control. Key permissions and replacement.
2. Add Plainrouter to the client
Create an MCP Client connection:- Choose + New MCP Server with URL
https://plainrouter.com/mcp. - Enter your Workspace key in API Key / Access token, then save. Plainrouter expects the credential as a bearer token.
- If the connection instead starts OAuth, complete Plainrouter sign-in and choose the account and access tier.
- Use Call a tool → get_install_instructions without arguments for the first production check. For AI tasks, use Execute an action with AI and initially expose only that tool.
3. Verify the connection
Start with this read-only request:Send conversions from a workflow
Conversion sending uses a separate HTTP request toPOST https://plainrouter.com/api/v1/events, authenticated with a Server secret, not an MCP Workspace key. Map the Conversion API body from a real eligible website event. Preserve its event ID and original time on retries, and supply the required consent and visitor context.
Start with the automation setup. An MCP read does not verify event delivery or attribution. Verify HTTP event acceptance and Meta delivery separately from the MCP connection.
4. Troubleshooting
- Wrong MCP app: use MCP Client to call Plainrouter. Make’s own MCP server exposes Make scenarios to other clients.
- 401 on a tool call: check the saved credential and selected connection; tool calls require workspace authorization.
- AI task does not call a tool: try Call a tool first, then check selected tools and AI provider access. A module’s accepted configuration is not a completed tool call.