Skip to main content
Choose your client and connect your Plainrouter workspace with a Workspace key or supported OAuth sign-in. Chat clients, terminal agents and workflow platforms use different configuration screens; the server and workspace boundaries stay the same.

Choose your setup guide

Endpoint and access

The unauthenticated sandbox is retired. Remove old test-server entries and configure the authenticated endpoint below. Create a Workspace key for the intended workspace or fixed set of workspaces. For multiple workspaces, use list_workspaces and pass workspace_id on subsequent tool calls. Read covers analysis; Actions previews and proposals require Write; new Read keys can inspect Actions records and policy. Keep credentials in protected client settings, never prompts or source control. OAuth clients obtain workspace-scoped execution credentials through sign-in instead of requiring a pasted key. Ask waits for approval; Full runs policy-allowed changes automatically. Rule violations are blocked either way. Client permission prompts do not override Plainrouter policy.

What proves the connection worked?

Inspect a real tool result: an authenticated read must return the intended workspace. A discovered tool list or an assistant saying “connected” does not prove authenticated access. Agent wording can vary, and connecting a client does not verify conversion delivery or ad execution. For another client, use the transport and authentication reference. For conversion sending without an agent, start with n8n and Make automation.