ASOHawk MCP server
Commit Nov 12, 2026Enables AI agents to analyze App Store rankings, track keywords, monitor competitors, and manage App Store Connect metadata and pricing.
Also known as prodocik/asohawk
- Stars
- 11
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.1
- Last commit
- Nov 12, 2026
- License
- —
What is ASOHawk MCP?
ASOHawk enables AI agents to analyze App Store rankings, track keywords, monitor competitors, and manage App Store Connect metadata and pricing.
Summary generated from the project's README
About ASOHawk MCP server
ASOHawk provides a remote MCP server that allows AI agents to manage App Store Optimization tasks directly. Designed for developers and app managers using clients like Claude Desktop, Cursor, or Claude Code, this service connects via HTTPS to provide deep insights into App Store rankings, keyword performance, and competitor activity. It functions as a hosted service, meaning there is no local database or installation required beyond adding a configuration block and an API key from asohawk.cc to your chosen client.
The platform includes 64 specialized tools that cover the entire ASO lifecycle, from monitoring review streams and revenue to executing metadata edits and pricing changes. To ensure security, the server uses scoped keys that separate read and write permissions. Any actions that modify your App Store Connect settings, such as changing screenshots or submitting builds for review, are treated as proposals that require human approval in a web dashboard before they go live.
What you can do with it
- 1Analyze competitor keyword strategiesAsk your agent to identify which keywords competitors are ranking for that your own app is missing.
- 2Generate growth and revenue reportsRequest a summary of your app performance and financial metrics for a specific time period.
- 3Manage App Store metadata and pricingInstruct an agent to update your app description or adjust subscription prices across different territories.
- 4Discover new keyword opportunitiesHave the AI find and track high-potential keywords to improve your app visibility.
Written from the project's README. Every use case is checked against a quote from it.
How to install ASOHawk MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall ASOHawk MCP in Claude Code
$ claude mcp add --transport http asohawk https://asohawk.cc/api/mcpInstall ASOHawk MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"asohawk": {
"url": "https://asohawk.cc/api/mcp"
}
}
}Install ASOHawk MCP in VS Code
.vscode/mcp.json
{
"servers": {
"asohawk": {
"type": "http",
"url": "https://asohawk.cc/api/mcp"
}
}
}Install ASOHawk MCP in VS Code CLI
$ code --add-mcp '{"name":"asohawk","type":"http","url":"https://asohawk.cc/api/mcp"}'Install ASOHawk MCP in Codex
$ codex mcp add asohawk --url https://asohawk.cc/api/mcpInstall ASOHawk MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.asohawk] url = "https://asohawk.cc/api/mcp"
Install ASOHawk MCP in Gemini CLI
$ gemini mcp add -s user --transport http asohawk https://asohawk.cc/api/mcpInstall ASOHawk MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"asohawk": {
"url": "https://asohawk.cc/api/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableprodocik/asohawk is public and reachablegithub.com/prodocik/asohawk ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-12github.com/prodocik/asohawk ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubASOHawk is an ASO platform your AI agent uses directly. It speaks MCP, the protocol Claude Code, Claude Desktop, Cursor, Codex and most agent CLIs already understand. Point an agent at it once and it reads your App Store rankings, keywords, competitors, reviews and revenue, and manages tracking and metadata on request.
The web dashboard exists too, but the agent is a first-class citizen, not an afterthought: every capability is a versioned tool with an explicit contract, honest limitations, and a safety model where anything that touches your App Store listing waits for your approval.
How it works
The server is remote MCP over HTTPS. Nothing to install, nothing to run, no local database: one config block in your client and the agent is connected.
Quick start
1. Create a key. Sign up at asohawk.cc (free plan, no credit card), then open Settings → API keys and create a key. Read by default; add write to let the agent manage tracking.
2. Connect. For Claude Code, run once in any terminal:
claude mcp add --transport http --scope user asohawk https://asohawk.cc/api/mcp --header "Authorization: Bearer ahk_YOUR_KEY"
Settings → Developer → Edit Config, then add:
{
"mcpServers": {
"asohawk": {
"type": "http",
"url": "https://asohawk.cc/api/mcp",
"headers": {
"Authorization": "Bearer ahk_YOUR_KEY"
}
}
}
}
Save as .cursor/mcp.json in your project, or ~/.cursor/mcp.json to make it available everywhere:
{
"mcpServers": {
"asohawk": {
"url": "https://asohawk.cc/api/mcp",
"headers": {
"Authorization": "Bearer ahk_YOUR_KEY"
}
}
}
}
Add to ~/.codex/config.toml:
[mcp_servers.asohawk]
url = "https://asohawk.cc/api/mcp"
[mcp_servers.asohawk.http_headers]
Authorization = "Bearer ahk_YOUR_KEY"
To keep the key out of the file, use codex mcp add with --bearer-token-env-var ASOHAWK_API_KEY instead.
Add to ~/.qwen/settings.json:
{
"mcpServers": {
"asohawk": {
"httpUrl": "https://asohawk.cc/api/mcp",
"headers": {
"Authorization": "Bearer ahk_YOUR_KEY"
}
}
}
}
kimi mcp add --transport http asohawk https://asohawk.cc/api/mcp --header "Authorization: Bearer ahk_YOUR_KEY"
Gemini CLI takes the same httpUrl block as Qwen Code in ~/.gemini/settings.json. VS Code takes a servers block in .vscode/mcp.json. Any client that reads mcp.json works with the standard shape:
{
"mcpServers": {
"asohawk": {
"type": "http",
"url": "https://asohawk.cc/api/mcp",
"headers": {
"Authorization": "Bearer ahk_YOUR_KEY"
}
}
}
}
Exact snippets for every client, plus a stdio bridge for clients without remote MCP support, are in the getting started guide.
3. Ask. The agent calls ASOHawk and answers in plain language:
Give me a growth report for my apps this week.
Who are my top competitors and which keywords do they rank for that I don't?
Find new keyword opportunities for my app and track the best ones.
How many downloads and how much revenue does https://apps.apple.com/us/app/duolingo/id570060128 get?
What the agent can do
64 tools cover the full ASO loop: rankings and keyword tracking, competitor discovery and monitoring, review streams, ASO health and recommendations, acquisition and retention funnels, revenue, keyword difficulty and popularity scoring, exact Apple Search Ads popularity on demand, chart moves, hypotheses and learnings, App Store Connect metadata edits, screenshot changes, native A/B tests (Product Page Optimization), paid-app, IAP and subscription repricing (one territory or a purchasing-power matrix across all 175), build attachment and App Review submission.
Every tool returns the same envelope: the answer under data, plus data_freshness, honest limitations, recommended_next_capabilities and a cost_class. Agents do not guess what a number means or what to call next; the response says so.
Lists inside data are tabular — {columns, rows} with positional cells — so a field name is written once, not once per row; the server states that reading rule in its instructions. Connecting with ?profile=core (or ?profile=keywords,changes) lists fewer tools up front without changing what the key may call: list_capabilities still names everything, marking what the profile left out.
- Tool reference: every tool with its contract, generated from the live registry.
- Playbooks: 16 step-by-step recipes, from onboarding an app to shipping a build through App Review.
- Concepts: authentication, permissions, the response envelope, errors, cost classes.
- Prompt library: copyable everyday prompts for setup, data, ASO work and safe execution.
Built for trust
- Scoped keys. Read keys see read tools only; write tools are invisible to them, not just refused.
- Human approval on writes. Metadata changes, screenshot changes, price changes and App Review submissions are proposals first. A human approves them in the dashboard before anything reaches App Store Connect. High-risk operations (name or description rewrites, prices, review submissions) wait for a human even in workspaces that enable auto-apply. The single exception, off by default and per call: a purchasing-power price matrix may run on auto when every territory already has a price and none of them moves more than 15%.
- Durable subscription repricing. A country-wide subscription matrix runs in the background with per-territory progress. It is marked applied only after a complete live App Store Connect read verifies every country; failed runs require an explicit reconciled resume, and ambiguous network outcomes are never retried blindly. Existing subscribers keep their price.
- Per-domain read controls. Each data domain can be switched off for agents independently.
- A closed error contract. Refusals carry a reason code, whether a retry can succeed, and alternative tools; agents recover instead of hallucinating.
Details in concepts.
Links
- Website and signup: asohawk.cc
- Live agent guide with your real key filled in: asohawk.cc/docs/agent
- Pricing: asohawk.cc/#pricing
ASOHawk is a hosted service; this repository is its public documentation. Found a gap or want a tool that is missing? Open an issue.
ASOHawk MCP questions
How do I add ASOHawk MCP to Claude Code?
Run claude mcp add --transport http asohawk https://asohawk.cc/api/mcp in your terminal. Add --scope user to make it available in every project.
How do I add ASOHawk MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Can the AI agent change my App Store metadata automatically?
The agent can propose changes, but high-risk operations like metadata edits, screenshot changes, and price changes require human approval in the dashboard before they reach App Store Connect.
What kind of data can the agent access?
The agent can read App Store rankings, keywords, competitors, reviews, revenue, and manage tracking and metadata.