astro

This Astro MCP Server provides a suite of tools that let you query Astro ASO data through the MCP protocol. The server exposes capabilities such as searching current keyword rankings, retrieving historical rankings, listing tracked apps, pulling keywords for a specific app, analyzing trends and opportunities, and identifying competitive landscapes. You can interact with these tools via MCP-enabled clients (for example Claude Desktop/Code) using natural language prompts like “show me the current rankings for the keyword ‘todo’ in the US store” or “list all apps currently tracked.” The tools are designed to work with Astro’s ASO database and return structured results you can feed into your own workflows, dashboards, or analysis pipelines. Mentioning tool names in your prompts (e.g., search_rankings, get_keyword_trends, analyze_competitive_landscape) will help the MCP client route questions to the correct capability and yield precise outputs.

Prerequisites:

• Astro app installed on macOS with data in Astro's database
• Node.js 18+ installed on your system

Installation steps:

1. Install Node.js (if not already installed):

   • macOS (with Homebrew): brew install node@18
   • Verify installation: node --version

2. Install the MCP server package (astro-mcp-server) globally or locally as preferred:

   • Using npm (global): npm install -g astro-mcp-server
   • Or using npx (recommended for running directly): npm install astro-mcp-server

3. Start the MCP server (standalone):

   • If installed globally: astro-mcp-server
   • Or via npx (no global install): npx astro-mcp-server

4. Optional: Build if you are using a local/source install and intend to run from dist/index.js:

   • cd /path/to/astro-mcp-server
   • npm run build
   • npm start

5. Connect an MCP client (Claude Desktop/Code, MCP Inspector) using the provided server name (astro) and the command/args shown above in the mcp_config.

Prerequisites recap:

• Astro installed and populated with data
• Node.js 18+
• Access to launch and run the astro-mcp-server process

Tips and common issues:

• Ensure Astro’s database file is accessible to the MCP server (path configured by Astro installation).
• If you encounter Node version mismatches with npx, you can specify the full path to your Node binary when configuring your MCP client as shown in the README examples.
• For Claude Desktop integration, you can place the following in your claude_desktop_config.json under mcpServers to point to npx astro-mcp-server or to a local dist index.js after building.
• The server supports both app name partial matching and exact app ID matching when querying apps and keywords.
• When using stand-alone or remote deployments, ensure firewall/network rules allow stdio MCP communication as required by your client.
• If you run into performance issues with large datasets, consider increasing Node.js memory limits and ensuring your Astro database is up-to-date with recent data.