AI Agent Integratie

MCP Documentatie

Verbind Appalize met Claude, Cursor en VS Code via het Model Context Protocol.

MCP Eindpunt Status Controleren

Ondersteuning voor duaal transport

Gebruik HTTP voor directe client calls of SSE wanneer uw MCP-client streaming events verwacht.

Assistant-ready tools

Stel trefwoord-, ranking-, app- en optimalisatie-workflows bloot aan AI-agenten via een enkele serverdefinitie.

Snelle onboarding

Plak een MCP-blok, voeg uw API-sleutel header toe en begin met testen vanuit de client die u al gebruikt.

Transport Eindpunten

Flexibele verbindingsmethoden.

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

Eindpunt Specificatie

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

Header:
x-api-key: YOUR_API_KEY

Standaard Configuratie

MCP JSON Definitie.

Serverconfiguratie

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

Clientconfiguratie

Eén integratie, oneindige workflows.

Elke client beheert MCP-configuratie anders. Gebruik de onderstaande stappen om Appalize met uw omgeving te verbinden.

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.

Toolmogelijkheden

Blootgestelde engine-operaties.

Onze MCP-server registreert automatisch gespecialiseerde tools voor uw AI-assistenten.

Capabiliteit

`search_keywords`

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

Capabiliteit

`get_app_details`

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

Capabiliteit

`get_competitor_keywords`

Inspect competitor keyword sets and ranking opportunities.

Capabiliteit

`optimize_title`

Generate AI-assisted title ideas using target keyword context.

Volgende Stappen

Klaar voor de REST API?

Ruwe datastromen of batchverwerking nodig? Onze REST API-documentatie biedt alle eindpuntdetails en playgrounds.

API-referentie Dashboard Openen