Applyra

io.applyraPublished by applyra.ioOfficial publisherv1.8.0Updated Oct 29, 2026

App Store Optimization data for AI agents: keyword ranks, scores, competitors, charts

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Applyra connects App Store and Google Play keyword data to an AI assistant for ASO research: ranks, difficulty scores, competitors, audits and charts.

What you can do
  • List and add tracked apps, and read ASO health scores and account usage
  • Track, untrack and favorite keywords, and inspect difficulty, traffic and related keywords
  • Mine autocomplete suggestions and cluster niche topics with opportunity scores
  • Read top charts by store, country, category and collection, plus rank and visibility history
  • Audit listing text, check metadata against store limits and simulate draft listings
  • Manage competitor pairs and chart notes, and compare visibility before and after each note
When to use it
Useful for indie developers and ASO work: researching keywords, auditing or drafting store listings, tracking rank and visibility over time, and checking whether a metadata change or campaign moved the numbers.
Requirements
Remote option: the hosted endpoint with OAuth sign-in, no install or API key. Local option: Node.js 20 or later, an Applyra account and an APPLYRA_API_KEY environment variable. A free plan allows 50 requests a month on 1 app, 5 keywords and 1 competitor; each tool call counts as one request.
Before you install
The local server needs an APPLYRA_API_KEY secret stored in the client configuration. Many tools write to the account: adding apps, tracking keywords, adding or removing competitors, and creating, editing or deleting notes. Usage is metered against plan limits, and paid plans may be needed for more requests or write tools in some clients.

Installation

In SourceWeft

  1. Open Applyra in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.applyra%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "applyra": {
      "type": "http",
      "url": "https://www.applyra.io/api/mcp"
    }
  }
}

README

@applyra/mcp-server

[npm] [CI] [License: MIT]

MCP (Model Context Protocol) server for Applyra. It connects your App Store and Google Play keyword data to AI assistants like ChatGPT, Claude, Cursor, Codex, VS Code Copilot, and more.

30 tools covering keyword rank tracking, difficulty and traffic scoring, listing audits and metadata simulation, competitor visibility, notes on your charts and what followed each one, autocomplete mining, niche clustering, and top charts, on the App Store and Google Play.

Remote server (ChatGPT, Claude, Gemini CLI, VS Code, Cursor)

The same tools are hosted at https://www.applyra.io/api/mcp (Streamable HTTP, OAuth). Nothing to install and no API key: the client opens an Applyra sign-in page, you approve it, and it is connected. It works with any Applyra account: the free plan includes 50 requests a month (each tool call is one request) on 1 app, 5 keywords and 1 competitor. Plan details are at applyra.io/pricing.

  • ChatGPT: on chatgpt.com, Plugins > Add > Create custom MCP server, with this URL and OAuth authentication, then Create as a plugin. Read and write tools both work on a ChatGPT Plus plan.
  • Claude: add it from the Claude directory in one click (on the web, desktop, mobile and in Claude Code), or as a custom connector with this URL (Customize > Connectors > Add custom connector).
  • Gemini CLI: gemini extensions install https://github.com/applyra-io/mcp-server, then sign in when Gemini CLI asks.
  • VS Code, Cursor, Perplexity, Smithery and any client that supports remote MCP servers with OAuth: add this URL as a remote (HTTP) server.

Connected assistants are listed, and can be disconnected, at applyra.io/dashboard/mcp.

Prerequisites (local server)

Installation

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

json
{  "mcpServers": {    "applyra": {      "command": "npx",      "args": ["-y", "@applyra/mcp-server"],      "env": {        "APPLYRA_API_KEY": "your_api_key"      }    }  }}

Cursor

Install the Applyra plugin from the Cursor Marketplace and set the APPLYRA_API_KEY environment variable. The plugin also ships an ASO research skill that guides the agent through the tools.

Or add the server manually to .cursor/mcp.json or ~/.cursor/mcp.json:

json
{  "mcpServers": {    "applyra": {      "command": "npx",      "args": ["-y", "@applyra/mcp-server"],      "env": {        "APPLYRA_API_KEY": "your_api_key"      }    }  }}

VS Code (GitHub Copilot)

Add to .vscode/mcp.json:

json
{  "servers": {    "applyra": {      "type": "stdio",      "command": "npx",      "args": ["-y", "@applyra/mcp-server"],      "env": {        "APPLYRA_API_KEY": "your_api_key"      }    }  }}

Claude Code

bash
claude mcp add applyra -e APPLYRA_API_KEY=your_api_key -- npx -y @applyra/mcp-server

Codex

Note --env, where Claude Code takes -e.

bash
codex mcp add applyra --env APPLYRA_API_KEY=your_api_key -- npx -y @applyra/mcp-server

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

json
{  "mcpServers": {    "applyra": {      "command": "npx",      "args": ["-y", "@applyra/mcp-server"],      "env": {        "APPLYRA_API_KEY": "your_api_key"      }    }  }}

Available Tools

ToolDescription
list_applicationsList tracked apps with store metadata, ratings, keyword count and ASO Health scores
add_applicationTrack a new application by its store bundle ID. Fetches store metadata and computes the initial visibility score
list_keywordsTracked keywords with current rank, favorite flag, difficulty/traffic scores
track_keywordsTrack up to 20 new keywords for an application in a single call
untrack_keywordStop tracking a keyword for an application (soft delete)
set_keyword_favoriteMark or unmark a tracked keyword as favorite for a specific app
inspect_keywordDeep-analyze any keyword: difficulty, traffic, KEI, top 20 apps, related keywords
list_keyword_inspectionsPast keyword inspections with their scores
run_autocompleteFetch autocomplete suggestions from the App Store or Google Play
list_autocomplete_historyPast autocomplete queries
run_niche_analysisCluster a niche topic into sub-niches with opportunity scores
list_niche_analysesPast niche analyses
top_chartsTop apps chart for a store/country/category/collection, with daily rank movement
list_top_chart_categoriesCategories and collections supported by top_charts, per store
get_keyword_rank_historyDaily rank evolution over a date range
get_app_score_historyDaily visibility score history for an app, with the notes and updates in the range
list_notesThe notes on an app's charts, numbered like their flags
add_noteNote what you did on a day (a campaign, a metadata change, a launch)
update_noteChange the text or the day of a note
delete_noteDelete a note
compare_eventsVisibility, or a keyword's rank, before and after each note and app update
get_aso_healthFull listing audit for an app: coverage, targeting and appeal, every field, and what to fix
check_metadataCheck draft listing text against each store's limits and forbidden copy. Instant, no store lookup
simulate_metadataScore a listing that does not exist yet and see the gain against the app's current score
list_metadata_simulationsListing drafts already scored on the account (titles and scores)
get_metadata_simulationOne saved draft in full: its four fields, its context and its findings
list_competitorsCompetitor pairs with side-by-side visibility scores
add_competitorAdd a competitor app to one of your applications by its store bundle ID
remove_competitorRemove a competitor relationship by its internal ID
get_account_usageCurrent usage vs. plan limits

Learn more

License

MIT. See LICENSE.

Source: README.md at commit 2ea3c6f

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

6
  1. v1.8.0LatestOct 29, 2026
  2. v1.7.0Oct 12, 2026
  3. v1.6.2Oct 7, 2026
  4. v1.6.1Oct 6, 2026
  5. v1.5.0Sep 17, 2026
  6. v1.4.2Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts