Skip to main content
Lite ASO
Browse documentation

MCP setup guide

Terminal agents

Use Codex for ASO research with Lite ASO

Codex can use LiteASO as a remote Streamable HTTP MCP server from its CLI, IDE extension, and desktop app through the shared Codex configuration.

Official Codex documentation

What you can do

Turn keyword findings into a reviewable metadata patch

Ask Codex to compare tracked keywords with competitor observations, then inspect the store metadata files in your repository. It can prepare a focused patch while you review the evidence and decide what to publish.

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 in a terminal. Codex writes the lite-aso server to its MCP configuration, so the same connection is available across Codex clients that share that config.

    Terminal
    codex mcp add lite-aso --url "https://mcp.liteaso.com/mcp"

    Codex documents remote HTTP and OAuth, but does not publish a per-server protocol-version guarantee. Update Codex and verify the connection before relying on it.

  2. Authorize your connection

    Run the login command and finish the LiteASO OAuth consent flow in your browser. Codex stores the resulting MCP credentials for the server.

    Command / client console
    codex mcp login lite-aso

  3. Check the connection

    List configured servers and confirm lite-aso is enabled. Inside an interactive Codex session, /mcp also shows the connection and exposed tools.

    Command / client console
    codex mcp list

  4. Try your first ASO task

    Paste this starting prompt into Codex, 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 tracked US keywords with its closest competitors, cite the available evidence, and rank the three best metadata opportunities.

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

Will one Lite ASO connection work across Codex clients?

Codex clients that share the same MCP configuration can use the saved lite-aso server. Run codex mcp list or open /mcp in the client you plan to use and confirm the server and tools are available there.

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.