Skip to main content

appstore-mcp

An open-source MCP server for live Apple App Store competitor research.

It lets AI agents search apps, fetch public App Store metadata, compare competitors side by side, and retrieve reviews and top charts as structured JSON — for market research, ASO research, and product analysis.

It works with public competitor data only. The default, recommended uvx setup below needs no Apple developer account, no API keys, and no database (a separate, optional hosted alternative does require an API key — see Hosted deployment).

Compare Duolingo, Babbel, and Busuu on the US Apple App Store.

Setup

Requires uv. Add to your MCP client config:

{
  "mcpServers": {
    "appstore": {
      "command": "uvx",
      "args": ["appstore-mcp"]
    }
  }
}
  • Claude Code: claude mcp add appstore -- uvx appstore-mcp, or install as a plugin: /plugin marketplace add LaurMost/appstore-mcp then /plugin install appstore-mcp
  • Claude Desktop: add the snippet above to claude_desktop_config.json
  • Cursor: add the snippet above to ~/.cursor/mcp.json

If your MCP client can't find uvx, use the absolute path from which uvx as the command.

Hosted deployment

The uvx setup above is still the primary, recommended way to use this server — it needs no API key. A hosted HTTP instance is also available at https://appstore-mcp.fastmcp.app/mcp for MCP clients that need a network-accessible endpoint instead of a local stdio process. It requires an API key, sent as an Authorization: Bearer <key> header. See docs/adr/0012-additive-hosted-http-mode.md for why this is additive rather than a replacement, and the trade-offs involved.

Tools

Tool What it does
search_app_store Search apps by keyword (slim results: id, name, developer, rating, price)
get_app_store_app Full public profile for one app: description, release notes, ratings, versions, screenshots, subtitle, in-app-purchase flag, privacy labels
compare_app_store_apps Batch-fetch several apps (IDs or URLs) side by side in one call
get_app_store_reviews Recent public customer reviews (up to ~500 per storefront)
digest_app_store_reviews Compress up to 500 reviews into a structured digest (themes, complaints, praise, sentiment) via MCP sampling — raw reviews never enter your context, and foreign-language storefronts are digested in English
get_app_store_screenshots An app's screenshots as actual images, so a multimodal model can analyze visual positioning, onboarding, and paywall design
get_app_store_charts Top-free / top-paid / top-grossing charts, overall or per category, per country

All tools are read-only and take a country storefront parameter (ISO 3166-1 alpha-2, default us). One MCP prompt, compare_competitors, packages the headline comparison workflow.

Responses are compact and normalized by default; get_app_store_app accepts include_raw=true when you want Apple's unmodified lookup payload.

Review digestion and MCP sampling

digest_app_store_reviews uses MCP sampling: the tool asks your client's LLM to compress the reviews, so no API key is needed. Not all MCP clients support sampling. If yours doesn't, either use get_app_store_reviews for raw reviews, or enable the server-side fallback:

uvx "appstore-mcp[anthropic]"   # + set ANTHROPIC_API_KEY
uvx "appstore-mcp[openai]"      # + set OPENAI_API_KEY

Set APPSTORE_MCP_SAMPLING_MODEL to override the fallback model. The digest is LLM-generated data reduction, not ground truth — quotes may be translated or paraphrased, and responses say so in meta.warnings.

Data sources and honest limitations

  • Primary source: Apple's public iTunes Search/Lookup API.
  • subtitle, has_iap, and privacy come from the public App Store web page; reviews and charts come from undocumented Apple feeds. These are best-effort: when they break or return nothing, tools degrade gracefully and say so in meta.warnings rather than failing or faking data.
  • Not available from public Apple data, so not provided: download counts, revenue estimates, keyword rankings, full review history, historical charts.
  • Apps are listed per-storefront: results, ratings, and reviews differ by country, and an app can exist in one storefront but not another.
  • Results are cached in-memory for ~15 minutes; meta.fresh tells you whether a response came from cache.

Development

uv sync --dev
uv run pytest          # offline fixture tests
uv run pytest -m live  # live smoke tests against real Apple endpoints
uv run mypy
uv run ruff check .    # lint
uv run ruff format .   # format (Black-compatible style)

fastmcp.json declares how to run the server from source (see Project Configuration). Use it to poke at the server directly, without a full MCP client:

fastmcp dev             # launch the MCP Inspector against local source (stdio)
fastmcp run             # run the server standalone (stdio)
fastmcp dev http.fastmcp.json  # same, but over HTTP on localhost:8000

Want a scriptable CLI instead of an MCP client? fastmcp generate-cli connects to a running server and writes a standalone typed CLI (plus an agent-ready SKILL.md) with one subcommand per tool - it queries over a live connection, so a fastmcp.json/stdio target doesn't work here; start the HTTP variant first, then point it at that:

fastmcp run http.fastmcp.json &
fastmcp generate-cli http://localhost:8000/mcp/ cli.py

The real hosted deployment (https://appstore-mcp.fastmcp.app/mcp, with an API key — see Hosted deployment) works as a generate-cli/fastmcp list/fastmcp call target too, if you'd rather point at that than spin up your own local HTTP server.

This is a local-iteration convenience only — the published package (uvx appstore-mcp) always runs over stdio via its own main() entrypoint, regardless of what's declared here.

Some tests assert full response shapes via inline-snapshot. After an intentional change to a tool's output shape, regenerate them:

uv run pytest --inline-snapshot=fix,create   # then review the diff

Optionally, verify the whole stack through a real MCP client — Claude Code driving the local server over stdio against live Apple:

uv run python scripts/claude_code_integration_test.py

This is a manual, on-demand check, not part of the default dev loop: it requires a logged-in claude CLI and spends real Anthropic API tokens per run.

This project is not affiliated with or endorsed by Apple. "App Store" is a trademark of Apple Inc.

License

MIT

Metadata

Release files for appstore-mcp 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for appstore-mcp 0.1.0
File Size Uploaded Provenance
appstore_mcp-0.1.0.tar.gz 366.1 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for appstore-mcp 0.1.0
File Interpreter ABI Platform
appstore_mcp-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 418.8 kB

Release files / appstore_mcp-0.1.0.tar.gz

Download URL appstore_mcp-0.1.0.tar.gz
Size 366.1 kB
Tags Source
SHA-256 checksum
How to use checksums
91fa3add48153ec697344224d1d2e4c6d377137689bc07aced9fb38d02ca3fc3
BLAKE2b-256 checksum
How to use checksums
ec2bb7a77c79d26b1b7ebefe69c2df32fc745a5bd3130f11c51fd242c371ca3a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 10, 2026.

Transparency log

Release files / appstore_mcp-0.1.0-py3-none-any.whl

Download URL appstore_mcp-0.1.0-py3-none-any.whl
Size 52.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4e30e693bf149077b62e2035e747fff89a60d01f89bbfc3bbdd9989e0959b772
BLAKE2b-256 checksum
How to use checksums
50dde1776a40b1e140b5d2a9686e8253fc6e6b6e9795c3756c3435feaf36e7bd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 10, 2026.

Transparency log

Security for appstore-mcp 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for appstore_mcp-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 10, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page