playablelabs-mcp-usage-cocos
PlayableLabs MCP Usage (Cocos)
Section titled “PlayableLabs MCP Usage (Cocos)”How to use the server: skill t1k-cocos-playable-playablelabs-mcp.
mcp__playablelabs__*is the PlayableLabs platform, not the Cocos editor (mcp__cocos-creator__*,mcp__cocos-mcp-server__*).- Call
whoamifirst. - Pass
organizationon every call when the credential covers several. - A destructive or write action returns
approval_required. Show the summary andapprovalUrlto the user and openapprovalUrlin their browser when one is available (xdg-openon Linux,openon macOS; skip on SSH/CI/no DISPLAY, just print it). Then, in the same turn and without waiting for a reply, do whatnextsays:confirm_action(handle), or for a large input the same tool again with exactly the same arguments plusconfirm: "<handle>". That call waits about 15 s; onapproval_pendingmake it again, and stop when the action runs, is refused or after about 10 minutes, then tell the user. The web approval page is the human approval: do not ask a second time in chat. - Never write a token into a repo, skill, rule or plan.
- Prod by default; dev or staging only when told.
- MCP is for interactive work; Jenkins PlayablePacker stays the CI path.