Koble Appalize til Claude, Cursor og VS Code via Model Context Protocol.
The assistant, API and MCP use the same operation registry. Discover what your account can access, inspect real data, then review the exact arguments of a proposed change.
Get the current input schema and required scopes. Follow nextOffset for additional results.
Read operations return data. Other operations create an unapplied proposal with a 15-minute approval window.
Approval executes the exact saved arguments. For queued work, check the job status separately.
search_platform_operations({
"query": "update_apple_ads_campaign", "limit": 5
})
// After reading the schema and resolving the actual campaign ID:
run_platform_operation({
"operation": "update_apple_ads_campaign",
"arguments": { "campaignId": 123, "dailyBudget": 25 }
})
// Nothing has changed yet. Show the proposal to the user.
// Only after explicit approval, use the returned proposal ID:
commit_platform_operation({
"proposalId": "<returned-proposal-id>", "approved": true
})
// On timeout, inspect this SAME proposal. Never prepare a duplicate.
get_platform_operation({ "proposalId": "<returned-proposal-id>" })| State | Meaning and next step |
|---|---|
| approval_required / pending | No operation has run. Review the arguments and approve or cancel. Preparation is not a provider dry run. |
| running | Execution has started. Read this proposal again. A process interruption can leave it running; inspect the affected resource before doing anything else. |
| succeeded | The handler returned successfully. A dry run is still a dry run; a returned job ID is not a completed job. Inspect the result. |
| failed / uncertain | A failure or timeout may leave partial changes. Inspect the provider resource. Never automatically create another proposal. |
| cancelled / expired | A pending proposal was cancelled or its approval window expired. No new execution can start from it. |
Research keywords and competitors, inspect Apple Ads reports and bids, prepare metadata and review replies, manage releases, TestFlight, subscriptions and screenshot projects. Personal notes and notifications use separate workspace scopes. Plan entitlements, ownership and provider permissions still apply.
The proposal ID is the idempotency key, bound to the same identity and channel. A repeated commit returns its state without repeating execution. Records are retained for seven days; a missing record is never replayed. Credentials, OAuth, binary uploads and administrative access remain in dedicated trusted interfaces.
Existing named MCP write tools retain their original behavior and may apply immediately. Configure your MCP client to request human approval, or use the reviewed operation workflow. Appi itself has no commit tool: the user approves in the chat review card.
Use audit_seo_document to check supplied HTML and compare_keyword_coverage to compare supplied SEO or ASO keyword lists. These tools do not crawl websites, grant access to a customer's Google Search Console or guarantee indexing, traffic or rankings. Use verified first-party SEO data alongside Appalize research; save content plans as notes without publishing automatically.
Where do I get the API key?
Create it in the Appalize product at API Dashboard, then paste it into your MCP client config as `x-api-key`.
HTTP: https://api.appalize.com/api/mcp
SSE: https://api.appalize.com/api/mcp/sse
Header:
x-api-key: YOUR_API_KEY{
"mcpServers": {
"appalize": {
"transport": "http",
"url": "https://api.appalize.com/api/mcp",
"headers": {
"x-api-key": "YOUR_API_KEY"
}
}
}
}Bruk HTTP for direkte klientkall eller SSE når MCP-klienten forventer strømmearrangementer.
Eksponer arbeidsflyter for søkeord, rangering, app og optimalisering til AI-agenter via en enkelt serverdefinisjon.
Lim inn en MCP-blokk, legg til din API-nøkkel og begynn å teste fra klienten du allerede bruker.
Hver klient håndterer MCP-konfigurasjon forskjellig. Bruk trinnene nedenfor for å koble Appalize til miljøet ditt.
Open Claude Desktop settings.
Add the Appalize MCP server entry to your config file.
Restart Claude Desktop and re-authorize with your API key.
Install Continue in VS Code.
Add an `mcpServers` entry pointing to the Appalize HTTP or SSE transport.
Reload the editor window to pick up the new tool server.
Enable MCP in Cursor settings.
Paste the Appalize MCP server definition with your API key.
Restart Cursor and test the manifest or health endpoint.
Appalize MCP is not a hand-maintained sidecar. The exposed catalog is filtered from the same registry and auth scope model that powers the backend integration layer.
The MCP manifest, tools, resources, and scopes are generated from one backend registry so the AI surface stays aligned with the product API.
Clients only see tools and resources their API key or dashboard JWT can actually use. Admin tools require an admin role as well as admin scopes.
The manifest omits input schemas unless `detail=full` is requested, reducing token usage for assistants that only need discovery.
Appalize MCP now spans keyword research, app details, competitor analysis, Apple workspace operations, pricing context, and other growth workflows.
Appalize publishes model-readable resources and prompts so an assistant can verify the active account, inspect scopes, follow the manifest-first flow, and use safer write behavior before it calls tools.
appalize://mcp/usage-guideTool/resource ordering, manifest-first discovery, ASO all-locale defaults, lowercase keyword policy, and safe write rules.
appalize://mcp/account-profileSafe metadata for the authenticated Appalize account: user ID, role, auth method, API key ID/name, label, and scopes. Raw secrets are never returned.
appalize://mcp/multi-account-guideClient config pattern and routing rules for multiple Appalize accounts.
appalize_mcp_orientationPrompt that tells the model to read account profile and usage guide resources before selecting tools, and to default ASO/cross-localization to all Appalize target locales unless a subset is explicit.
appalize_multi_account_routingPrompt that tells the model to verify account context and ask before ambiguous writes.
Create a separate Appalize API key for each Appalize account or client profile, then give each key its own MCP server name. The backend does not store other Appalize account keys for routing.
{
"mcpServers": {
"appalize-personal": {
"transport": "http",
"url": "https://api.appalize.com/api/mcp",
"headers": {
"x-api-key": "APK_FOR_PERSONAL_ACCOUNT"
}
},
"appalize-client-a": {
"transport": "http",
"url": "https://api.appalize.com/api/mcp",
"headers": {
"x-api-key": "APK_FOR_CLIENT_A"
}
},
"appalize-client-b": {
"transport": "http",
"url": "https://api.appalize.com/api/mcp",
"headers": {
"x-api-key": "APK_FOR_CLIENT_B"
}
}
}
}search_keywordsLook up keywords and suggestions with country-aware query support.
get_app_detailsFetch app records and related analytics context for a store identifier.
get_competitor_keywordsInspect competitor keyword sets and ranking opportunities.
optimize_titleGenerate AI-assisted title ideas using target keyword context.