MCP and AI tools

AppsXi gives your AI coding tool two Model Context Protocol servers and a set of instructions:

Remote server at https://appsxi.com/api/mcp: the docs, integration guides, license helper code, appxi.json validation, and, with your API token, your apps, builds, denial explanations, listing, pricing, chart positions, the sandbox, and your orders, licenses and reviews.
Local server (npx appxi mcp): checks your project and installers on your machine (stack, signing setup, secrets, outside checkout links, preflight, manifest and workflow generation).
Skills and rules: appxi-integrate, appxi-package, appxi-publish, appxi-fix-denial, appxi-requirements and appxi-test for Claude Code, a Cursor rule, and an AGENTS.md section for Codex and other tools.

Quick setup

In your project folder:

Terminal

npx appxi ai

It writes .claude/skills/appxi-*, .cursor/rules/appxi.mdc, the AppsXi section of AGENTS.md (between  and , the rest of the file is untouched) and adds both servers to .mcp.json. Use --claude, --cursor or --agents for just one, --no-mcp to leave .mcp.json alone, and --force to replace skills you edited. The files are also at /ai/manifest.json if you prefer to copy them yourself.

Remote server

Claude Code:

Terminal

claude mcp add --transport http appxi https://appsxi.com/api/mcp --header "Authorization: Bearer $APPXI_TOKEN"

Cursor (.cursor/mcp.json) and other clients that speak Streamable HTTP:

JSON

{ "mcpServers": { "appxi": { "url": "https://appsxi.com/api/mcp", "headers": { "Authorization": "Bearer ${env:APPXI_TOKEN}" } } } }

The token is optional: without it the docs tools work and the account tools tell the assistant to ask for one. Create tokens in Developer → API tokens. Tick Can use the sandbox for the sandbox tools and Can read orders, licenses and reviews for the data tools. A token never lets an assistant change prices, listings, payouts or publishing, and no tool returns a buyer's name or email: buyers appear only as an id that is stable within one app.

Tool	Needs	What it does
`search_docs`	nothing	Best matching sections of these docs.
`get_doc`	nothing	One docs page as Markdown.
`get_integration_guide`	nothing	Steps for a stack (swift, electron, tauri, dotnet, juce, flutter) and a feature (packaging, licensing, trials, checkout, updates, publishing).
`get_code_snippet`	nothing	The license helper for typescript, swift, cpp or csharp.
`get_sdk_versions`	nothing	API, manifest, helper, CLI and MCP versions and the deprecation policy.
`validate_manifest`	nothing	Checks an `appxi.json` and explains each error and warning.
`explain_check`	nothing	The fix for a pipeline finding.
`list_apps`, `list_builds`	token	Your apps and their recent builds.
`get_build_report`, `explain_denial`	token	A build's findings, in plain language, with the fix for each.
`get_listing`, `get_pricing`, `get_rankings`	token	Read only; changes happen in the dashboard.
`create_test_license`, `simulate_trial`, `list_test_licenses`	sandbox token	Sandbox licenses and trial time travel (advance, expire, convert, revoke, restore).
`list_orders`, `list_licenses`, `list_reviews`	data token	Your orders, licenses and reviews, oldest first, 50 at a time, filtered by app, dates and live or sandbox. Same fields as the Developer API.

Prompts: make_appxi_ready, add_trial, fix_denied_build, setup_github_publishing, migrate_licensing. The docs and helper files are also exposed as resources (appxi://docs/<page>, appxi://sdk/<file>).

Local server

Terminal

claude mcp add appxi-local -- npx -y appxi mcp

Tool	What it does
`detect_stack`	Electron, Tauri, Swift, .NET, JUCE, Flutter or unknown, with evidence.
`scan_for_secrets`	Hardcoded live keys in a folder, with masked samples.
`scan_for_checkout_links`	Outside checkout links that a paid AppsXi build must not have.
`check_signing_setup`	Developer ID identities and notarytool, or a Windows code signing certificate.
`preflight_package`	The full `appxi check` on an installer.
`generate_manifest`	`appxi.json` from an installer.
`generate_github_action`	The publish workflow for a stack.
`list_apps`, `get_build_report`	Same as the remote tools (set `APPXI_TOKEN`).
`search_docs`	Searches these docs.

Prompts that work well

"Make this app AppsXi ready with a 7 day trial."
"Check my project for anything AppsXi would reject."
"Set up AppsXi publishing for this repo."
"Why was build 1234… denied? Fix it."