AI-agentintegrasjon

MCP-dokumentasjon

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

MCP-endepunkt Sjekk status

Støtte for dobbel transport

Bruk HTTP for direkte klientkall eller SSE når MCP-klienten forventer strømmearrangementer.

Assistentklare verktøy

Eksponer arbeidsflyter for søkeord, rangering, app og optimalisering til AI-agenter via en enkelt serverdefinisjon.

Rask onboarding

Lim inn en MCP-blokk, legg til din API-nøkkel og begynn å teste fra klienten du allerede bruker.

Transport-endepunkter

Fleksible tilkoblingsmetoder.

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

Endepunktspesifikasjon

HTTP: https://api.appalize.com/api/mcp
SSE:  https://api.appalize.com/api/mcp/sse

Header:
x-api-key: YOUR_API_KEY

Standardkonfigurasjon

MCP JSON-definisjon.

Serverkonfigurasjon

{
  "mcpServers": {
    "appalize": {
      "transport": "http",
      "url": "https://api.appalize.com/api/mcp",
      "headers": {
        "x-api-key": "YOUR_API_KEY"
      }
    }
  }
}

Klientoppsett

Én integrasjon, uendelige arbeidsflyter.

Hver klient håndterer MCP-konfigurasjon forskjellig. Bruk trinnene nedenfor for å koble Appalize til miljøet ditt.

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, which keeps assistants inside the right permission boundary.

Current workflow coverage

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

Verktøykapasiteter

Eksponerte motoroperasjoner.

Kapasitet

`search_keywords`

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

Kapasitet

`get_app_details`

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

Kapasitet

`get_competitor_keywords`

Inspect competitor keyword sets and ranking opportunities.

Kapasitet

`optimize_title`

Generate AI-assisted title ideas using target keyword context.

Neste steg

Klar for REST API?

API-referanse Åpne dashbord