---
name: playmos-game-integration
description: Integrate only the Playmos services a developer chooses, keeping their engine, backend and existing game.
---
# Integrate a game through Playmos MCP

Use the developer’s existing game and engine. Keep their backend and code-defined products unless they ask to change them. Do not create a second game for a store or feature.

## 1. Choose what Playmos handles

Read `playmos_get_brief` and `playmos_get_game_integration`. Ask only for missing choices, then save changes with `playmos_set_game_integration` using the current version. Playmos services are optional and can be mixed with the developer’s backend.

## 2. Complete the next required step

Call `playmos_get_next_step`. Read `playmos_get_service_setup` only when setup is needed; preserve existing settings and use its current revision when saving. `playmos_get_game_services` reports actual runtime checks, not selected providers. Request a focused example with `playmos_get_integration_example` only for the feature being added.

- **Playmos purchases:** keep products in code and export public IDs and prices in `playmos-iap.json` for a ZIP, or choose catalogue items. Keep backend item delivery unless Playmos inventory is requested. Register server-owned prices; verify payment before delivering an item once. Reuse the original order and payment on a retry.
- **Your own checkout or competitions:** keep their existing verification and backend. No Playmos catalogue is needed for external checkout; no Playmos entry fees or prize splits are needed for external competitions.
- **Playmos competitions:** use the saved rules and server score verification. Paid entry also needs confirmed payment and backend admission. A rehearsal is not a paid competition.
  Saving rules and submitting them for Playmos review use the Playmos account, with no blockchain signature. Read the selected provider and saved status before suggesting signing. Playmos-managed pool registration is a Playmos setup task. For a developer-selected external pool, explain the chain, contract, method, amount and purpose of its concrete transaction before requesting wallet approval.
- **Controllers:** keep keyboard/touch working; add other inputs where they fit. Phone pairing requires a real authenticated session.

`playmos_configure_game_services` registers supported worlds or vehicle garages. It does not register purchase products or activate a generic competition. Keep private keys on the backend. Use a supported SDK checkout host; do not weaken Studio’s sandbox or invent a private payment protocol when transport is unavailable.

## 3. Test and request release

Test the services actually used. Purchases need cancellation with no item delivered, pending-payment recovery, and duplicate callbacks with one delivery. Test competition verification only when competitions are selected. Report local tests, hosted checks and confirmed payments separately.

Read `playmos_get_publishing_guide` for release. Saving choices does not activate services or publish. Publisher approval, wallet permission and public publication remain separate actions.

## Install this skill

`playmos_get_agent_skill` returns the relative skill files and checksums. Save them under the agent host’s skills directory, preserve the folder name, and reload skills there. Never include credentials.