AI-agentintegration

MCP Dokumentation

Forbind Appalize til Claude, Cursor og VS Code via Model Context Protocol.

MCP Endepunkt Tjek status

Understøttelse af dobbelt transport

Brug HTTP til direkte klientkald eller SSE, når din MCP-klient forventer streaming-begivenheder.

Assistant-ready tools

Eksponér søgeords-, rangerings-, app- og optimerings-workflows til AI-agenter via en enkelt serverdefinition.

Hurtig onboarding

Indsæt en MCP-blok, tilføj din API-nøgle-header, og begynd at teste fra den klient, du allerede bruger.

Transport-endepunkter

Fleksible forbindelsesmetoder.

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`.

Endepunktsspecifikation

HTTP: http://backend-p844sww08cccoo4oo84ck0kc:5000/api/mcp
SSE:  http://backend-p844sww08cccoo4oo84ck0kc:5000/api/mcp/sse

Header:
x-api-key: YOUR_API_KEY

Standardkonfiguration

MCP JSON Definition.

Serverkonfiguration

{
  "mcpServers": {
    "appalize": {
      "transport": "http",
      "url": "http://backend-p844sww08cccoo4oo84ck0kc:5000/api/mcp",
      "headers": {
        "x-api-key": "YOUR_API_KEY"
      }
    }
  }
}

Klientopsætning

Én integration, uendelige workflows.

Hver klient håndterer MCP-konfiguration forskelligt. Brug trinene herunder til at forbinde Appalize til dit miljø.

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json

Open Claude Desktop settings.

Add the Appalize MCP server entry to your config file.

Restart Claude Desktop and re-authorize with your API key.

VS Code / Continue

~/.continue/config.json

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.

Cursor

~/.cursor/mcp.json

Enable MCP in Cursor settings.

Paste the Appalize MCP server definition with your API key.

Restart Cursor and test the manifest or health endpoint.

Registry & scopes

How the MCP surface stays current.

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.

Registry-driven surface

The MCP manifest, tools, resources, and scopes are generated from one backend registry so the AI surface stays aligned with the product API.

Scope-filtered catalog

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.

Compact by default

The manifest omits input schemas unless `detail=full` is requested, reducing token usage for assistants that only need discovery.

Current workflow coverage

Appalize MCP now spans keyword research, app details, competitor analysis, Apple workspace operations, pricing context, and other growth workflows.

Model context resources

Give the assistant runtime instructions from MCP itself.

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-guide`

Tool/resource ordering, manifest-first discovery, ASO all-locale defaults, lowercase keyword policy, and safe write rules.

`appalize://mcp/account-profile`

Safe 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-guide`

Client config pattern and routing rules for multiple Appalize accounts.

`appalize_mcp_orientation`

Prompt 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_routing`

Prompt that tells the model to verify account context and ask before ambiguous writes.

Multiple Appalize accounts

Use one MCP server entry per Appalize account.

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.

Read appalize://mcp/account-profile before account-specific work.

If the user does not specify an account and a write tool may be called, ask which profile to use.

Do not mix apps, drafts, campaigns, subscriptions, screenshots, or reports across server entries unless explicitly requested.

Multiple account MCP JSON config

{
  "mcpServers": {
    "appalize-personal": {
      "transport": "http",
      "url": "http://backend-p844sww08cccoo4oo84ck0kc:5000/api/mcp",
      "headers": {
        "x-api-key": "APK_FOR_PERSONAL_ACCOUNT"
      }
    },
    "appalize-client-a": {
      "transport": "http",
      "url": "http://backend-p844sww08cccoo4oo84ck0kc:5000/api/mcp",
      "headers": {
        "x-api-key": "APK_FOR_CLIENT_A"
      }
    },
    "appalize-client-b": {
      "transport": "http",
      "url": "http://backend-p844sww08cccoo4oo84ck0kc:5000/api/mcp",
      "headers": {
        "x-api-key": "APK_FOR_CLIENT_B"
      }
    }
  }
}

Værktøjskapaciteter

Eksponerede motoroperationer.

Vores MCP-server registrerer automatisk specialiserede værktøjer til dine AI-assistenter.

Kapacitet

`search_keywords`

Look up keywords and suggestions with country-aware query support.

Kapacitet

`get_app_details`

Fetch app records and related analytics context for a store identifier.

Kapacitet

`get_competitor_keywords`

Inspect competitor keyword sets and ranking opportunities.

Kapacitet

`optimize_title`

Generate AI-assisted title ideas using target keyword context.

Næste skridt

Klar til REST API?

Brug for rå datastrømme eller batchbehandling? Vores REST API-dokumentation giver alle endepunktsdetaljer og legepladser.

API-reference Åbn Dashboard