Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

ASOHawk

by prodocikversion 0.1.1i★ –iRuns in the cloud
Registry nameio.github.prodocik/asohawk

Install

Overview

Description from the maker (original English)

ASO analytics and App Store optimization tools for indie iOS developers and AI agents.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Marketing & social media

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: Authorization

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http asohawk https://asohawk.cc/api/mcp --header 'Authorization: Bearer {api_key}'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "asohawk": {
      "url": "https://asohawk.cc/api/mcp",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "asohawk": {
      "type": "http",
      "url": "https://asohawk.cc/api/mcp",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • Authorization HTTP header
    ASOHawk workspace API key created in Settings > API keys

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account prodocik, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Marketing & social mediai

  • More stars than 0% of the other 2956 servers in this category
  • Published to the registry more recently than 23% of the other 2956 servers in this category
  • Basic checks equal to or better than 100% of the other 2956 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is ASOHawk safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

An MCP server retrieving transcripts of YouTube videos

Runs on your computer★ 495MITUpdated 9 days ago
Install

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

Runs on your computer★ 244MITUpdated 9 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

App Store Optimization, built for AI agents.

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

Claude Desktop

Settings → Developer → Edit Config, then add:

{

"mcpServers": { "asohawk": { "type": "http", "url": "https://asohawk.cc/api/mcp", "headers": { "Authorization": "Bearer ahk_YOUR_KEY" } } } }

Cursor

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

Codex

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.

Qwen Code

Add to ~/.qwen/settings.json:

{

"mcpServers": { "asohawk": { "httpUrl": "https://asohawk.cc/api/mcp", "headers": { "Authorization": "Bearer ahk_YOUR_KEY" } } } }

Kimi CLI

kimi mcp add --transport http asohawk https://asohawk.cc/api/mcp --header "Authorization: Bearer ahk_YOUR_KEY"

Gemini CLI, VS Code and any other MCP client

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](TOOLS.md): every tool with its contract, generated from the live registry.
  • [Playbooks](docs/playbooks.md): 16 step-by-step recipes, from onboarding an app to shipping a build through App Review.
  • [Concepts](docs/concepts.md): authentication, permissions, the response envelope, errors, cost classes.
  • [Prompt library](docs/prompts.md): 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

ASOHawk is a hosted service; this repository is its public documentation. Found a gap or want a tool that is missing? Open an issue.

Ask PopNx