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: https://api.appalize.com/api/mcp
SSE:  https://api.appalize.com/api/mcp/sse

Header:
x-api-key: YOUR_API_KEY

Standardkonfiguration

MCP JSON Definition.

Serverkonfiguration

{
  "mcpServers": {
    "appalize": {
      "transport": "http",
      "url": "https://api.appalize.com/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, 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.

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