Skip to main content
Lite ASO
Browse documentation

MCP setup guide

Terminal agents

Compare storefront ASO data from Gemini CLI

Gemini CLI supports remote Streamable HTTP servers, automatic OAuth discovery, and user- or project-scoped MCP settings.

Official Gemini CLI documentation

What you can do

Compare visibility observations across target countries

Ask Gemini CLI to examine the same app across selected storefronts and call out only differences supported by country-specific observations. Use the comparison to decide which market deserves a closer listing review.

Before you start

Sign in to Lite ASO and add the app you want to work on. Keep its store, app identifier and target country handy. The Connect page in your dashboard contains account-specific connection settings and agent keys when needed.

Sign in to Lite ASO
MCP server URL
https://mcp.liteaso.com/mcp

  1. Add Lite ASO

    Run the add command to save LiteASO in ~/.gemini/settings.json at user scope. Start a new Gemini CLI session after changing the configuration.

    Terminal
    gemini mcp add --scope user --transport http lite-aso "https://mcp.liteaso.com/mcp"

    Gemini CLI documents HTTP OAuth discovery but not compatibility with every protocol revision. Update the CLI and verify a read request first.

  2. Authorize your connection

    Inside Gemini CLI, run /mcp auth lite-aso and complete the browser flow. OAuth needs a local browser and a reachable localhost callback.

    Command / client console
    /mcp auth lite-aso

  3. Check the connection

    Run the list command in your shell and confirm lite-aso reports Connected. In Gemini CLI, /mcp shows the available server tools.

    Command / client console
    gemini mcp list

  4. Try your first ASO task

    Paste this starting prompt into Gemini CLI, then replace the app and country with your own. Ask the agent to explain any missing data before continuing.

    Example ASO prompt
    Use LiteASO to compare my app's visibility across the US, UK, and Turkey, and explain only differences supported by country-specific evidence.

You stay in control. Review the proposed metadata or review reply before publishing. Sensitive actions follow Lite ASO’s server-side approval policy; a chat instruction does not bypass it.

Troubleshooting

Why does Gemini CLI OAuth fail after the browser opens?

The OAuth flow needs a local browser and a reachable localhost callback. Run /mcp auth lite-aso from the machine where Gemini CLI is running, then retry after checking local network or browser restrictions.

The server will not connect

Check that the URL ends in /mcp and uses HTTPS. Update your client and check its support for protocol 2026-07-28. Older protocol versions are rejected; changing to an SSE or stdio configuration will not fix this. Check your client’s official documentation for network or workspace restrictions.

Sign-in fails or authorization expires

Reconnect using the client’s authentication command or connector settings and sign in to the intended Lite ASO account. For an agent key, manage or replace it from the dashboard Connect page. Keep keys out of shared files and source control.

The agent cannot see my app or tools

Check the server is enabled and the intended tools are allowed in your client. Confirm that the app belongs to the Lite ASO account you authorized, and specify its store, app identifier and country. Reconnect after changing permissions; do not assume missing data is a zero result.

Use a client version that supports remote Streamable HTTP, Lite ASO authentication and MCP protocol 2026-07-28. These guides describe client configuration; availability varies by version, account and workspace policy, and is not a compatibility certification.