AI-agentintegration

MCP-dokumentation

Anslut Appalize till Claude, Cursor och VS Code via Model Context Protocol.

MCP-slutpunkt Kontrollera status

Stöd för dubbel transport

Använd HTTP för direkta klientanrop eller SSE när din MCP-klient förväntar sig strömmande händelser.

Assistant-ready verktyg

Exponera arbetsflöden för sökord, ranking, app och optimering för AI-agenter via en enda serverdefinition.

Snabb onboarding

Klistra in ett MCP-block, lägg till din API-nyckel i headern och börja testa från klienten du redan använder.

Transport-endpoints

Flexibla anslutningsmetoder.

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

Endpoint-specifikation

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"
      }
    }
  }
}

Klientinställningar

En integrering, oändliga arbetsflöden.

Varje klient hanterar MCP-konfiguration olika. Använd stegen nedan för att ansluta Appalize till din 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.

Verktygets förmågor

Exponerade motoroperationer.

Förmåga

`search_keywords`

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

Förmåga

`get_app_details`

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

Förmåga

`get_competitor_keywords`

Inspect competitor keyword sets and ranking opportunities.

Förmåga

`optimize_title`

Generate AI-assisted title ideas using target keyword context.

Nästa steg

Redo för REST API?

API-referens Öppna instrumentpanel