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 a custom connector forhttps://plainrouter.com/mcp.
Plainrouter accepts Authorization: Bearer … with the workspace key. If your connector exposes bearer/header configuration, keep the key there, never in the conversation. If Grok starts a Plainrouter OAuth sign-in instead, sign in and choose the intended account and Read or Write access; that issues a workspace-scoped OAuth credential without pasting a key. A manually created key is not needed for that route.
Grok’s published setup specifies a server URL followed by authentication; it does not specify a universal manual-header field. Do not paste your key into the URL to work around a missing field.
3. Verify the connection
Start with this read-only request:4. Troubleshooting
- Connector creation is unavailable: check organization provisioning with your Grok administrator.
- Authentication is requested: use Plainrouter sign-in or the client’s protected bearer setting. Do not use a Management key or Server secret.
- A summary appears without data: inspect the actual tool result. Ask explicitly for the connector and read-only tool; a connected label alone is not a successful read.