Integració d'AI Agent

Documentació de MCP

Connecta Appalize a Claude, Cursor i VS Code.

Suport Dual Transport

Utilitza HTTP o SSE.

Eines preparades per a l'assistent

Exposa fluxos de treball als AI Agents.

Onboarding ràpid

Afegeix la teva clau d'API i comença.

Transport

Mètodes de connexió flexibles.

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

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

Header:
x-api-key: YOUR_API_KEY
Configuració estàndard

Definició MCP JSON.

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

Una integració, infinits fluxos de treball.

Connecta Appalize al teu client.

Claude Desktop

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

1

Open Claude Desktop settings.

2

Add the Appalize MCP server entry to your config file.

3

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

VS Code / Continue

~/.continue/config.json

1

Install Continue in VS Code.

2

Add an `mcpServers` entry pointing to the Appalize HTTP or SSE transport.

3

Reload the editor window to pick up the new tool server.

Cursor

~/.cursor/mcp.json

1

Enable MCP in Cursor settings.

2

Paste the Appalize MCP server definition with your API key.

3

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.

Capacitat de les eines

Operacions.

Eines especialitzades per a assistents d'IA.

Capacitat

search_keywords

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

Capacitat

get_app_details

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

Capacitat

get_competitor_keywords

Inspect competitor keyword sets and ranking opportunities.

Capacitat

optimize_title

Generate AI-assisted title ideas using target keyword context.

Següents passos

Llest per a l'API REST?

Tots els detalls sobre els endpoints.