Connect your agent to Playmos.
Use Codex, Claude or Grok to manage your studio’s contest plans through the same permissions as the publisher workspace.
One server URL#
https://test.playmos.io/api/mcp
Transport: Streamable HTTP. Authentication: OAuth authorization code with PKCE S256. Sign in with your Playmos account and approve the requested access. You do not copy an API key or a session cookie into your agent.
Check connection configuration. An enabled server still needs a successful real client sign-in before it is considered verified.
Codex#
codex mcp add playmos --url https://test.playmos.io/api/mcpcodex mcp login playmoscodex mcp list
Complete browser sign-in. Use /mcp to check the connection. If the operator uses preregistration, add --oauth-client-id YOUR_PUBLIC_CLIENT_ID when adding the server and register the exact callback Codex displays. Automatic setup requires the OAuth provider’s client registration support.
Official Codex MCP instructions
Claude#
claude mcp add --transport http playmos https://test.playmos.io/api/mcpclaude# In Claude Code, run /mcp and authenticate Playmos.
For a preregistered public client, add --client-id YOUR_PUBLIC_CLIENT_ID --callback-port 8080. Register the exact localhost callback required by your installed version. Public clients need no client secret. Claude’s remote connector interfaces can use the same URL; verify the actual client flow before rollout.
Official Claude Code MCP instructions
Grok#
- Open Grok Connectors.
- Choose New Connector → Custom.
- Enter the server URL above and complete authentication.
Business and Enterprise teams may need their team admin to provision the connector first. The endpoint must be public HTTPS. This release’s Grok OAuth compatibility still needs a real connection test.
Official Grok connector instructions
Your first request#
List my Playmos studios, then list contest plans for Playmos Labs.Do not create or submit anything yet.
Your existing studio membership determines what you can access. A successful connection grants no admin role. Ask to create or change a contest only after checking the studio and saved rules.
Available controls#
| Control | What happens |
|---|---|
| List studios and contests | Read your current memberships and owned contest plans. |
| Create or edit a contest plan | Set the entry fee, duration, prize split and winner shares. Existing plans require their saved version. |
| Submit a contest | Send the current plan for independent review. |
| Check publication readiness | See which release requirements remain blocked. |
These are saved plans. Opening, funding, cancelling, settling or paying a live pool is not implemented in this MCP release. App publication remains gated by frozen hosting, security checks and SDK verification.
Choose permissions#
| OAuth scope | Access |
|---|---|
| publisher:read | List studios, read contest plans and check release readiness. |
| publisher:edit | Create and edit plans; also request publisher:read. |
| publisher:submit | Submit plans for review; also request publisher:read. |
The server also checks your current studio role for every action. Removing that role removes tool access even while an OAuth token is still valid.
Connection help#
| Symptom | Next step |
|---|---|
| 503: OAuth not configured | The Playmos operator must enable the MCP API and deploy the configured service. |
| 401: sign-in required | Authenticate again. The server accepts only a valid OAuth access token for this exact MCP URL. |
| 403: access denied | Check consent scopes and your studio membership. Extra scopes cannot create a missing studio role. |
| Client registration error | Enable provider client-ID metadata support, or use an operator-provided registered public client. |
| 409: revision changed | Read the latest contest plan before saving or submitting. |
| No publishing or settlement tool | Those live operations are not available in this release. |
Operator setup#
Configure standard OAuth once
Use the existing Auth0 provider with a dedicated API identifier matching the MCP URL, RS256 access tokens, PKCE S256, explicit user consent and the scopes above. Enable supported client-ID metadata discovery and import approved clients, or preregister public clients with exact callbacks. Enable Auth0’s Resource Parameter Compatibility Profile in tenant Settings → Advanced so the standard OAuth resource parameter selects this API audience. Verify that binding; do not change a shared tenant’s default audience as a shortcut.
Set PLAYMOS_MCP_AUDIENCE to the exact MCP URL on the Hub service. Keep the existing Auth0 issuer. Metadata is at /.well-known/oauth-protected-resource/api/mcp; unauthorized requests advertise it in a Bearer challenge. Test each client’s browser consent, token refresh and revoked membership on the deployed build.
OAuth interoperability requirements · Auth0 resource parameter setup · Auth0 client-ID metadata setup