For agent harnesses
PlayaOS in OpenClaw and Hermes
The gift layer isn't just for chat apps. OpenClaw, Hermes, and any other agent harness can reach PlayaOS two ways: natively over MCP, or through the open-source skill pack and CLI. Paste one prompt and your agent sets itself up.
Two ways to plug in
MCP server recommended
OpenClaw and Hermes both speak MCP natively. Point the harness at https://api.playaos.app/mcp with a personal pk_user key and your agent gets the full, always-current tool surface — nothing to install or keep in sync.
Skill pack + CLI
For harnesses, scripts, and cron jobs that can't attach an MCP server, the playaos/ai-toolkit repo ships skills/playaos/SKILL.md — a skill pack your agent can read — plus the @playaos/cli with a stable JSON and exit-code contract, wrapping the same API.
Copy, paste, connected
One prompt per harness. Create a free account first so you have a personal key to hand over.
OpenClaw
Connect this OpenClaw agent to PlayaOS over Streamable HTTP at https://api.playaos.app/mcp.
Read https://playaos.app/docs/mcp for setup instructions.
Use OAuth when the client supports it: discover the authorization server and sign in to PlayaOS.
For clients that cannot use OAuth, send Authorization: Bearer <personal pk_user_* key from https://playaos.app/dashboard/developer>.
An org pk_live_* key is for camp integrations, not personal access. Keep personal keys out of source control and logs.
List the available tools and confirm access with a read of my packing list before making changes.
You can search events and art, manage my packing list, and use the marketplace. Camp access follows my membership and role; connecting never grants additional permissions.Hermes
Connect this Hermes agent to PlayaOS over Streamable HTTP at https://api.playaos.app/mcp.
Read https://playaos.app/docs/mcp for setup instructions.
Use OAuth when the client supports it: discover the authorization server and sign in to PlayaOS.
For clients that cannot use OAuth, send Authorization: Bearer <personal pk_user_* key from https://playaos.app/dashboard/developer>.
An org pk_live_* key is for camp integrations, not personal access. Keep personal keys out of source control and logs.
List the available tools and confirm access with a read of my packing list before making changes.
You can search events and art, manage my packing list, and use the marketplace. Camp access follows my membership and role; connecting never grants additional permissions.Agent setup FAQ
- Do OpenClaw and Hermes work with PlayaOS?
- Yes. Both harnesses speak MCP natively, so the recommended setup is the remote PlayaOS MCP server at api.playaos.app/mcp with OAuth or a personal key — no install, always current. For harnesses or scripts that can't attach an MCP server, the open-source ai-toolkit repo ships a skill pack (skills/playaos/SKILL.md) and the @playaos/cli that wrap the same API.
- What can an agent do once it's connected?
- Search Burning Man events, art installations, the public camp directory, and the marketplace; manage your packing list down to which tote each item is in; post listings; and, for camps you belong to, answer questions about your shifts and campmates. An agent only ever sees what your account can see.
- Does it cost anything?
- No. A free PlayaOS account is all you need — there are no paid tiers. Requests are rate-limited to 60 per minute.
- Where do keys come from?
- Personal pk_user keys come from the developer dashboard at playaos.app/dashboard/developer. Camp-scoped pk_live keys (for building on a camp's data) come from the platform console under Developer → API Keys.
The gift is ready when you are.
Give your camp a free portal, or take the free playa tools into ChatGPT and Claude. Either way, it costs nothing.
Building your camp's site yourself? The API, SDKs, and UI kit are part of the gift too.