playablelabs-mcp-usage
PlayableLabs MCP Usage
Section titled “PlayableLabs MCP Usage”Applies whenever an agent calls mcp__playablelabs__* tools (the PlayableLabs platform server).
Advisory: a kit ships no hooks. Setup, workflow and errors: skill t1k-playablelabs-base-mcp.
- Call
whoamifirst. - Pass
organizationon every call when the credential covers several. - A destructive call returns
approval_requiredwith asummaryandapprovalUrl. Show both and open the URL in the user’s browser if one is available (xdg-open/open; just print it on SSH, CI or no DISPLAY). Then, in the same turn and without waiting for a reply, follownext:confirm_actionwith the handle, or the same tool again with exactly the same arguments plusconfirm: "<handle>". It waits about 15 s; onapproval_pendingrepeat the call. Stop when the action runs, is refused, or after about 10 minutes, then tell the user. The web page is the human approval: never ask again 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.