Dual transport support
Use HTTP for direct client calls or SSE when your MCP client expects streaming events.
Connect Appalize to Claude, Cursor, and VS Code through the Model Context Protocol.
Use HTTP for direct client calls or SSE when your MCP client expects streaming events.
Expose keyword, ranking, app, and optimization workflows to AI agents through one server definition.
Paste one MCP block, add your API key header, and start testing from the client you already use.
HTTP: https://backend.appalize.com/api/mcp
SSE: https://backend.appalize.com/api/mcp/sse
Header:
x-api-key: YOUR_API_KEY{
"mcpServers": {
"appalize": {
"transport": "http",
"url": "https://backend.appalize.com/api/mcp",
"headers": {
"x-api-key": "YOUR_API_KEY"
}
}
}
}Each client handles MCP configuration differently. Use the steps below to connect Appalize to your environment.
Open Claude Desktop settings.
Add the Appalize MCP server entry to your config file.
Restart Claude Desktop and re-authorize with your API key.
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.
Enable MCP in Cursor settings.
Paste the Appalize MCP server definition with your API key.
Restart Cursor and test the manifest or health endpoint.
Our MCP server registers specialized tools automatically for your AI assistants.
search_keywordsLook up keywords and suggestions with country-aware query support.
get_app_detailsFetch app records and related analytics context for a store identifier.
get_competitor_keywordsInspect competitor keyword sets and ranking opportunities.
optimize_titleGenerate AI-assisted title ideas using target keyword context.
Next Steps
Need raw data streams or batch processing? Our REST API documentation provides full endpoint details and playgrounds.