MCP: connect your AI assistant
MCP lets an AI assistant use connections configured in Fox Store to query apps, maintain store content, and run implemented upload and release operations. MCP calls Engine business capabilities; CLI serves CI/CD release automation. They share the engine but expose different tool scopes.
Enable and prepare
- Install the latest Fox Store, activate your license, and add a Provider connection.
- Open Settings → MCP and enable MCP. The switch saves immediately and survives restarts; permission and timeout changes require Save.
- Review connections, execution permissions, and available tools under Permissions.
- Copy the client configuration under Connection method, add it to your AI client, and reconnect MCP.
The installer includes a native MCP executable; no separate Node.js or MCP plugin is needed. The client starts an independent process over local stdio. After initialization, the Fox Store desktop need not remain open. Renew an expired license lease through the desktop.
Configure your AI client
Use the generated TOML for Codex. Local clients such as Claude Code can use the generated JSON as a reference, following their own configuration format. Use the absolute executable path, arguments, and data directory shown in Settings, not someone else's paths.
In a form, enter the command separately and add --data-dir and its directory path as two separate arguments. Do not paste quotes, commas, or a whole array into one argument. Linux AppImage configurations may also include --mcp; preserve the complete generated configuration. Provider secrets are not needed in the client configuration.
Compatibility depends on local stdio MCP support in the client. Models such as GLM, DeepSeek, and Gemini need a compatible client; web or cloud products accepting only remote URLs cannot run your local executable directly. No HTTP service address is currently provided.
Permissions and tools
| Permission | Allowed operations |
|---|---|
| Read only (default) | Query connections, apps, versions, and status without changing platform data. |
| Content maintenance | Includes reading; allows copy and asset updates, but excludes review submission, release, deletion, and account permission changes. |
| Release management | Includes content maintenance; permits supported tools for review submission, release, deletion, pricing, distribution, and account permissions. |
All connections, including future ones, are allowed by default. You can select specific connections and override their default permission. Tools are selected by default; manual deselections are preserved. Group counts mean enabled tools / total tools, not platform menu counts. Expand a group to inspect tools and required permissions.
Connection scope, tool switches, execution permissions, and platform account permissions all apply. Selecting a tool does not grant write access. Higher permissions cannot add capabilities missing from the platform or Engine. There is no per-call desktop approval; your AI client may request confirmation separately. Results may be sent to the client's model service.
Example requests
- “List apps, latest versions, and Chinese descriptions for this App Store connection; explicitly mark missing information.”
- “Check the test Track and release status of this Google Play app.”
- “Update this app's Chinese store description with this text.”
- “Preflight this local package, then upload it to the selected connection's testing channel.”
Specify the connection, app, language, and channel. Queries return only account-visible data; unavailable capabilities or insufficient permissions produce errors. Upload success does not mean approval or a live release. See CLI / API reference for pipelines.
Images and local files
Save AI-generated images on the computer running MCP, then provide an absolute file path and target app. Cloud chat images or sandbox paths may not be readable locally. Correct missing files, access problems, or invalid formats according to the error.
Operations depend on the platform and tool: store artwork and icons inside a package are different. Apple's primary app icon must ship with a new build; an image cannot directly replace the icon of a published app.
Troubleshoot connections and calls
- No tools or only old tools: check the switch, tool selections, and saved settings; reconnect the client. After upgrades, exit the old MCP process and reconnect.
- Cannot start: check the executable, separate arguments, and outdated installation paths; copy fresh settings. “Executable ready” indicates its presence, not a connected client.
- MCP_POLICY_INVALID: update Fox Store, reload and save the policy in Settings, then reconnect. If it persists, retain the error for diagnosis; do not delete the credential database.
- Connection or credentials unavailable: verify the data directory and selected connection, and check the connection and system credential store in the desktop. Different OS users cannot directly share credentials.
- License, permission, or timeout errors: refresh the license and check required and platform permissions. Long tasks may also need a higher client timeout. If a write result is unknown, check platform status before resubmitting.
Recent calls shows tool, outcome, and duration summaries. See Provider connections and Troubleshooting.