App Store & Play Store MCP Server

FetchLayer runs a single Model Context Protocol (MCP) server at https://mcp.fetchlayer.dev that gives any MCP-compatible AI agent direct access to public app reviews on both the Apple App Store and Google Play — no scraper code, no per-platform API keys to juggle. The same server also exposes tools for FetchLayer’s other live platforms (Reddit, X/Twitter, YouTube, Google Maps), so an agent already connected to FetchLayer for one platform has both app stores available on the same connection.

This page covers what the App Store and Google Play tools do, how to connect them in the clients developers use most, and what to ask your agent once it’s wired up.

What the server can do

Together these cover the two things most review-monitoring or competitive-research workflows need: finding an app (App Store search) and pulling its review history (App Store or Google Play reviews), all as structured JSON — rating, review text, author, date, app version where available.

Get an API key

Every client needs a FetchLayer API key. Get one free — no credit card required.

Connect it to your client

Every client below uses the same server URL (https://mcp.fetchlayer.dev) and the same Authorization: Bearer ss-your-api-key header. Only the config file location changes.

Claude Desktop

Edit (or create) claude_desktop_config.json:

{
  "mcpServers": {
    "fetchlayer": {
      "url": "https://mcp.fetchlayer.dev",
      "headers": {
        "Authorization": "Bearer ss-your-api-key"
      }
    }
  }
}

Fully restart Claude Desktop (not just close the window) so it picks up the new server.

Cursor

Cursor reads MCP configs from mcp.json, either globally (~/.cursor/mcp.json) or per-project (.cursor/mcp.json). Add:

{
  "mcpServers": {
    "fetchlayer": {
      "url": "https://mcp.fetchlayer.dev",
      "headers": {
        "Authorization": "Bearer ss-your-api-key"
      }
    }
  }
}

Reload the window afterward. If you already have other MCP servers configured, add the "fetchlayer" block alongside them rather than replacing the file.

Claude Code

Fastest path — add it via the CLI:

claude mcp add fetchlayer \
  --transport streamable-http \
  https://mcp.fetchlayer.dev \
  -- --header "Authorization: Bearer ss-your-api-key"

This saves to ~/.claude/settings.json globally. Add --scope project before the URL to scope it to .mcp.json in the current project instead. You can also edit either file by hand with the same mcpServers block shown above for Claude Desktop.

Other MCP clients (Windsurf, VS Code, etc.)

Any client that supports the MCP Streamable HTTP transport works the same way: point it at https://mcp.fetchlayer.dev with the same Bearer header. The config file location is the only thing that differs — check your client’s MCP documentation for where it lives.

What to ask your agent

A few things worth trying once it’s connected:

• “Search the App Store for [competitor app] and pull its most recent reviews.” The agent chains scrape_appstore_search to find the App Store ID, then scrape_appstore_reviews to fetch its reviews — two tool calls, no manual ID lookup on your end.
• “Compare what users complain about on the App Store version vs. the Google Play version of this app.” Run scrape_appstore_reviews and scrape_playstore_reviews for the same app and let the agent contrast the two platforms’ feedback.
• “Pull the last month of Google Play reviews and group them into bugs, feature requests, and praise.” scrape_playstore_reviews returns structured data the agent can categorize directly, without you reading through the App Store or Play Store console yourself.

Because both tools return structured JSON rather than store pages, the agent doesn’t need to parse or paginate anything by hand — it goes straight from “check these reviews” to reasoning about what’s in them.

Pricing

MCP usage is billed the same as the REST API: a free tier with no credit card required (50 requests/month via MCP), then pay-as-you-go at $1.99 per 1,000 requests, or a monthly subscription starting at $25/mo if your usage is predictable. See the full pricing page for subscription tiers.

Common issues

• Tools not showing up in your client? Double-check the config file path for your OS/tool, validate the JSON (watch for trailing commas), and fully restart the app rather than just reloading a window.
• “Invalid API key” errors? Confirm the key starts with ss- and was copied in full from the FetchLayer dashboard.
• Need REST instead of MCP? See the App Store Reviews API and Google Play Reviews API references for direct HTTP access to the same data.

What’s Next

• MCP for every FetchLayer platform — the full server overview, all 6 platforms in one place
• App Store Reviews API — the underlying REST API and endpoint reference
• Google Play Reviews API — the underlying REST API and endpoint reference
• Reddit MCP Server — the same setup pattern for Reddit data