Connect ASO Skill with MCP.

One hosted endpoint works with ChatGPT, Claude, and other remote MCP clients. The client discovers OAuth, opens ASO Skill for sign-in and consent, then receives short-lived, refreshable access.

https://api.asoskill.com/mcp

Available tools

search_app_store

Current ranked search results and keyword difficulty

1 credit
get_keyword_popularity

Current 1–100 keyword popularity and source

1 credit
lookup_app_store_apps

Detailed metadata for up to ten App Store IDs

1 credit
get_credit_balance

Available and used account credits

Free
list_credit_packs

Current pack IDs, quantities, and prices

Free

Authentication without copied API keys

  1. The MCP client discovers ASO Skill's protected-resource and OAuth metadata.
  2. It dynamically registers itself and starts authorization code with S256 PKCE.
  3. You sign into ASO Skill and approve data and credits access.
  4. The client receives a one-hour access token and a rotating refresh token. Your password and long-lived API keys are never shared.

Protocol details

The endpoint uses MCP Streamable HTTP over HTTPS and OAuth 2.1-style authorization. It supports dynamic client registration, exact resource binding, refresh-token rotation with reuse detection, revocation, and stateless MCP requests. Every tool publishes an output schema, OAuth metadata, and safety annotations.

The server also exposes the installable ASO Skill through the MCP skills extension. ChatGPT can import a versioned snapshot during plugin scanning, while Claude and other clients continue to use the tools normally.

Connections appear in the developer dashboard with their scopes, last use, tool-call count, and credit use. Disconnecting there revokes the complete access-and-refresh token family.

Use the MCP Inspector when integrating another client. The HTTP API remains available through the developer guide.