mcpField
A
appindex

appindex

Local
github.com/CloudCorpRecordsBusiness & Marketing0Updated 1w ago

About appindex

appindex is a local bridge to the hosted AppNiche service, giving agents live App Store and Google Play data. It forwards searches, app history, listing changes, keyword scores, and review queries without keeping a local app catalog.

Key features

  1. 01Search apps across both stores
  2. 02Retrieve app details and metric history
  3. 03View listing-change timelines
  4. 04Score keyword difficulty and opportunity
  5. 05Read reviews and supported countries

Use cases

  1. 01Filter apps by category, rating, or downloads
  2. 02Track app metrics and listing redesigns
  3. 03Compare keyword competition
  4. 04Review app feedback and sentiment topics

MCP support

It runs as an MCP server, exposing the hosted AppNiche MCP tool list to MCP clients and forwarding tool calls upstream. Results are returned unchanged.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"cloudcorprecords-appindex": {
"command": "npx",
"args": [
"-y",
"@reneturcios/appindex"
]
}
}
}
Run commandnpx -y @reneturcios/appindex

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@reneturcios/appindex0.1.0
ocighcr.io/cloudcorprecords/appindex:0.1.0

Tools

8

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
gamesanyNotrue: games only, on both stores — the App Store 'Games' category and every Google Play game category. Narrow with 'game_genres'.
limitintegerNoHow many apps to return, 1-100. If omitted: 20 for assistant sign-in connections, 50 with an API key. Each returned app costs 1 credit, so ask for the page size you need; when the balance is lower, the page shrinks to the balance.
storeanyNoLimit results to one store: 'apple' (App Store) or 'google' (Google Play). Omit to search both.
offsetintegerNoHow many apps to skip before returning results; use for paging.
searchanyNoFree-text query matched against app title and developer name, e.g. 'calorie tracker'.
sort_byenumNoColumn to sort by: 'downloads' (default), 'revenue', 'growth', 'reviews', 'rating', 'title', 'released' or 'updated'.downloads | revenue | growth | reviews | rating | title | released | updated
categoryanyNoStore category name to filter by, e.g. 'Health & Fitness', 'Productivity', 'Games'. Use 'categories' to include several at once.
languageanyNoSingle app-language code the listing supports, e.g. 'en', 'de', 'pt-BR'.
sort_direnumNoSort direction: 'desc' (default, highest first) or 'asc'.asc | desc
languagesanyNoSeveral app-language codes to include, e.g. ['en', 'es'].
search_inanyNoWhich field 'search' matches: 'title', 'developer', or 'all' (default). Use 'developer' to list a publisher's portfolio.
categoriesanyNoSeveral category names to include, e.g. ['Health & Fitness', 'Lifestyle']. Takes precedence over 'category'.
max_ratinganyNoHighest average star rating to include, 0-5; use to find weak incumbents.
min_ratinganyNoLowest average star rating to include, 0-5, e.g. 4.
game_genresanyNoGames of these genres, named alike on both stores, e.g. ['Puzzle', 'Role Playing', 'Strategy'] (also Action, Adventure, Arcade, Board, Card, Casino, Casual, Educational, Family, Music, Racing, Simulation, Sports, Trivia, Word). Implies 'games'.
max_revenueanyNoHighest estimated monthly revenue in USD, e.g. 50000 for $50K/month.
max_reviewsanyNoHighest lifetime review count, e.g. 1000 to exclude entrenched giants.
min_revenueanyNoLowest estimated monthly revenue in USD, e.g. 10000 for $10K/month.
min_reviewsanyNoLowest lifetime review count, e.g. 1000.
price_modelanyNoMonetisation model: 'Free', 'Freemium' or 'Paid'. Case-insensitive on input.
growth_metricanyNoMetric the growth filter measures — currently only 'reviews'.
growth_periodanyNoWindow growth is measured over: '7d', '14d', '30d', '60d' or '90d', for both stores. Google Play apps are measured every few weeks, so their 14-90 day growth is pro-rated from each app's nearest earlier measurement and covers far more Play apps than '7d' does.
max_downloadsanyNoHighest estimated monthly downloads.
min_downloadsanyNoLowest estimated monthly downloads, e.g. 10000.
not_languagesanyNoLocalization-gap filter: return only apps NOT localized in any of these language codes, e.g. ['it'] finds apps without an Italian localization. App Store data only — combine with languages=['en'] to shortlist English apps missing a target market's language.
updated_afteranyNoOnly apps last updated on or after this date, 'YYYY-MM-DD'.
min_growth_pctanyNoLowest absolute growth percentage over 'growth_period', e.g. 20 for at least ±20%.
released_afteranyNoOnly apps released on or after this date, 'YYYY-MM-DD'.
updated_beforeanyNoOnly apps last updated on or before this date, 'YYYY-MM-DD'.
released_beforeanyNoOnly apps released on or before this date, 'YYYY-MM-DD'.
growth_directionanyNoKeep only apps growing ('up') or declining ('down') over 'growth_period'.
max_days_since_updateanyNoOnly apps updated within this many days, e.g. 30 for actively maintained apps.
max_days_since_releaseanyNoOnly apps first released within this many days, e.g. 90 for fresh launches.

Details

From the project README

appindex

appindex is a small local bridge to the hosted AppNiche MCP server, which exposes live App Store and Google Play data. Search both stores across more than twenty-five filters, pull one app's full record, read its historical metrics and its listing-change timeline, score keywords for difficulty and opportunity, read app reviews, and list the supported country codes — all from your agent, with no local copy of the catalogue.

The bridge keeps no app data of its own. It serves the upstream server's tool list locally, exactly as captured from the live endpoint, and forwards each tool call upstream, returning the result untouched. A few tools state a per-call credit cost in their descriptions; those credits are charged by the upstream service against the caller's own pre-existing AppNiche account. There is no tool here that buys credits, creates an account, or mints a key, and the bridge adds none.

Tools

  • search_apps — search App Store and Google Play apps across filters for store, category, games and game genres, language (including a not_languages localization-gap filter), price model, rating, review count, download and revenue estimates, release and update recency, and review-growth direction, sorted by any column. Every filter is optional.
  • get_app_detail — return one app's full record. Required: app_id (a canonical id such as "apple:284882215" or "google:com.spotify.music", a bare Apple track id, an Android package name, or a store URL).
  • get_app_historicals — return historical metric points for one app, daily up to 90 days and weekly beyond. Required: store_id. Optional: store, days.
  • get_app_timeline — return one app's listing change history, newest first: versions, icon and screenshot redesigns, price and business-model changes, renames, category moves, description rewrites and more, grouped by day. Required: store_id. Optional: store, days, before.
  • get_keyword_difficulty — score one keyword for difficulty and opportunity on the App Store or Google Play. Required: keyword. Optional: store, country, language.
  • batch_keyword_difficulty — score up to 10 keywords in one call. Required: keywords. Optional: store, country, language.
  • get_app_reviews — read app reviews: pass app_id for live store reviews of any app, or omit it to read the workspace's tracked apps with sentiment, topics and improvement areas attached. Every argument is optional.
  • get_supported_countries — return the supported country codes. Takes no arguments.

Configuration

  • APPNICHE_MCP_URL (optional) — override the upstream endpoint. Defaults to https://api.getappniche.com/mcp. (The override hook is this rebuild's own labelled reconstruction.)
  • GETAPPNICHE_API_KEY (optional) — when set, every upstream request carries an Authorization: Bearer <key> header, for the caller's own AppNiche key created in their AppNiche dashboard settings. When it is not set, no key header is sent. (The header name and the env name are pinned by the original's registry record; the Bearer scheme and this env forwarding are labelled reconstructions — the original surface was captured keyless.)
Forwarding mechanics

On the first tool call the client opens a streamable HTTP session with the upstream: a JSON-RPC initialize request (protocolVersion 2025-03-26, clientInfo name appindex), then a notifications/initialized notification, then the tools/call request carrying the caller's arguments unchanged. When the upstream answers initialize with an Mcp-Session-Id header, that value rides on every later request of the session, which is reused for the life of the process. Replies may arrive as plain JSON or as server-sent events; both are read.

Successful upstream results pass through verbatim, including any isError flag the upstream sets. Failures — a JSON-RPC error, a non-2xx status, an unreadable response, or a request that cannot be completed — come back as an isError result whose text starts with appindex error: (this rendering is this rebuild's own labelled reconstruction).

CLI

Each tool is also a subcommand taking one JSON argument string:

npx @reneturcios/appindex search_apps '{"search":"calorie tracker","store":"apple","limit":10}'
npx @reneturcios/appindex get_app_detail '{"app_id":"apple:284882215"}'
npx @reneturcios/appindex get_keyword_difficulty '{"keyword":"habit tracker"}'
npx @reneturcios/appindex get_supported_countries
npx @reneturcios/appindex --version

Exit codes: 0 on success, 1 on an isError result, 2 on a usage error.

MCP server

npx -y @reneturcios/appindex mcp

MCP client config:

{
  "mcpServers": {
    "appindex": {
      "command": "npx",
      "args": ["-y", "@reneturcios/appindex", "mcp"]
    }
  }
}

Docker

docker run -i ghcr.io/cloudcorprecords/appindex
docker run --rm ghcr.io/cloudcorprecords/appindex --version

The container's default command is mcp, so the first form is a stdio MCP server; any other arguments reach the CLI normally.

Development

npm install
npm run build
npm test
npm run dev

The test suite runs entirely against a stubbed JSON-RPC upstream — no live network calls.

License

MIT — see LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.