MCP server
FRVR Developers has a hosted Model Context Protocol (MCP) server. Connect your AI assistant to it and manage your games through conversation, with the same permissions you have in FRVR Developers.
What you can do
Section titled “What you can do”| Area | What the assistant can do |
|---|---|
| Games & settings | Find your studios and games. Update descriptions, categories and ad settings. |
| Builds & QA | Inspect versions and QA results. Upload new builds and get a QA link. |
| Artwork & video | Check asset requirements, upload files and generate the supported variants. |
| In-app purchases | List, create, update and delete products in your IAP catalog. |
Publishing a game to a channel is not available through MCP; do that in FRVR Developers.
Connect your assistant
Section titled “Connect your assistant”- In your assistant’s MCP settings, add a remote server named FRVR Developers with the URL above. The client needs to support Streamable HTTP and OAuth.
- Connect, sign in with your FRVR Developers account and approve access. Your assistant handles authentication; there is no API key to create or paste.
- Try asking: “Find my games and list their latest versions.”
Claude Code
Section titled “Claude Code”Run the commands with the CLI installed and complete sign-in in your browser.
Every call is checked against your account: you only reach studios you are a member of, and their games.
| Tool | Arguments | Result |
|---|---|---|
list_studios | None | The studios you are a member of |
list_games | studioId | All games of that studio |
get_game_details | gameId | The game’s identity and editable metadata |
update_game_details | gameId, data | The saved details, after applying only the fields you sent |
list_game_versions | gameId | All versions, including archived ones, newest first |
create_game_version_upload_url | gameId | Temporary upload URL, upload key, PUT headers, size limit |
finalize_game_version | gameId, version, uploadKey, optional notes | The created version, a QA link and QA readiness |
list_game_asset_types | Optional category | Asset types, file requirements and how variants derive from each other |
list_game_assets | gameId | Current assets and their URLs |
create_game_asset_upload_url | gameId, assetType, contentType | Temporary upload URL, upload key, PUT headers, size limit |
finalize_game_asset | gameId, assetType, uploadKey | The uploaded asset and every generated variant |
list_game_iap_products | gameId | All IAP products of the game |
create_game_iap_product | gameId, sku, name, price, optional type, description, currency | The created product |
update_game_iap_product | gameId, productId, data | The saved product, after applying only the fields you sent |
delete_game_iap_product | gameId, productId | Confirmation that the product was permanently deleted |
Prices are integer USD cents.
Editing game details
Section titled “Editing game details”-
Call
get_game_detailswith a game id fromlist_gamesto read the current values. -
Call
update_game_detailswith adataobject holding only the fields to change:
Editable fields are description, descriptionShort, tagline, orientation, category, engine, flexibleAspectRatio, adsInterstitial, adsRewarded, adsBanner and rewardedAdFailPopup. Fields you leave out keep their value. The game name is read-only, and saving details does not publish or rebuild anything.
Uploading a build or an asset
Section titled “Uploading a build or an asset”Uploads take three steps, the same for builds and assets:
- Ask for an upload URL:
create_game_version_upload_urlorcreate_game_asset_upload_url. PUTthe raw file bytes to the returneduploadUrlwith the returned headers. A build is a ZIP withindex.htmlat its root.- Finish with
finalize_game_versionorfinalize_game_asset. A finished build returns a QA link; a finished asset returns its generated variants.
If a finalize call times out, check list_game_versions or list_game_assets before trying again.