ASOClimb in your AI assistant

What the connection can do

Every tool is a thin wrapper over the same routes the ASOClimb web app uses, so results, plan limits and provenance labels are identical whichever surface you ask from. Rankings and listing facts come from storefront observations; traffic, difficulty, KEI, visibility and opportunity scores are models and are labelled as such in every response.

Typical requests once connected: "Which of my tracked keywords moved this week?", "Inspect the keyword habit tracker in the US App Store", "Show the top free Productivity apps in Germany", "What is the keyword gap between my app and this competitor?", "Analyse the niche sleep sounds on Google Play".

Connect from Claude (web, desktop and mobile)

Claude connects through OAuth: you sign in to ASOClimb and approve the workspace, and no key is typed anywhere.

1. Open Claude → Settings → Connectors (under Customize) → Add → Add custom connector.
2. Name it ASOClimb and enter the server URL https://asoclimb.com/mcp. Leave the OAuth client fields empty; Claude registers itself.
3. Click Add, then Connect. Sign in to ASOClimb with Google or Apple if asked, choose whether to allow write access, and click Allow.
4. Back in Claude, the ASOClimb tools appear under the connector. Read-only tools run without a prompt; tools that change the workspace or spend allowance ask first.

Connect from ChatGPT

ChatGPT uses the same OAuth flow through its custom MCP server support (a paid ChatGPT plan is needed).

1. Open ChatGPT → Settings → Apps & Connectors (or Plugins) → Advanced → enable Developer mode.
2. Choose Add custom MCP server, name it ASOClimb, enter https://asoclimb.com/mcp, keep Authentication on OAuth and create it.
3. Sign in to ASOClimb when the approval page opens and click Allow. Mention ASOClimb in a chat to use it.

Claude Code, Cursor, Windsurf and Codex

Command-line and editor clients work with OAuth where they support it, and otherwise with a workspace API key from Account → Developer in ASOClimb. A key can be read-only.

Add to Cursor (one click)Add to VS Code

Claude Code

claude mcp add --transport http asoclimb https://asoclimb.com/mcp

Cursor / Windsurf (mcp.json)

{ "mcpServers": { "asoclimb": { "url": "https://asoclimb.com/mcp" } } }

Codex (~/.codex/config.toml)

[mcp_servers.asoclimb]
url = "https://asoclimb.com/mcp"

With an API key instead of OAuth

{ "mcpServers": { "asoclimb": { "url": "https://asoclimb.com/mcp", "headers": { "Authorization": "Bearer ark_live_…" } } } }

What you approve, and what it costs

A connection is scoped to one workspace and to one of two permission levels, which you choose on the approval page. workspace:read lets the assistant read tracked apps, keywords, ranks and history, saved inspections, competitors, charts and usage. workspace:write additionally lets it track or untrack apps and keywords, add competitors, and run keyword inspections, autocomplete and niche analyses — the live checks that count against your plan’s monthly allowance.

Each tool call is one API request against the plan’s monthly API allowance, exactly like a request made with an API key; protocol traffic (listing tools, pings) is free. Usage per connection is shown under Account → Developer, where any connection can be disconnected. Access tokens expire after an hour and are refreshed automatically; refresh tokens expire after 30 days without use.

The tools

Read-only tools (run without confirmation):

get_account_usage, get_capabilities, search_store, list_applications, get_application, list_keyword_opportunities, list_keywords, get_keyword_rank_history, list_keyword_inspections, get_keyword_inspection, list_autocomplete_history, list_niche_analyses, list_competitors, get_competitor_keywords, list_top_chart_categories, top_charts, list_new_release_categories, new_releases, get_app_score_history, get_dashboard, get_scheduler_health, list_alert_events, get_metadata, simulate_metadata, list_metadata_drafts, compare_metadata_draft, check_listing_metadata, get_keyword_gap, list_keyword_gaps.

Tools that change the workspace or spend allowance (clients ask before running them):

add_application, discover_keywords, track_keyword_opportunities, track_keywords, untrack_keyword, set_keyword_favorite, inspect_keyword, run_autocomplete, run_niche_analysis, add_competitor, remove_competitor, get_category_rank, save_metadata_draft, expand_keyword_gap.

For developers

Transport: MCP Streamable HTTP, JSON responses, stateless, at https://asoclimb.com/mcp (protocol revisions 2024-11-05 through 2025-06-18 and later). Authorization: OAuth 2.1 authorization-code grant with PKCE (S256), RFC 9728 protected-resource metadata at /.well-known/oauth-protected-resource, RFC 8414 server metadata, RFC 7591 dynamic client registration for public and confidential clients, RFC 8707 resource indicators, rotating refresh tokens and RFC 7009 revocation. A bearer workspace API key is accepted as an alternative.

Questions, bug reports and data requests: support@asoclimb.com. The privacy policy describes exactly what a connected assistant receives.