Skip to main content
Lite ASO
Browse documentation

MCP setup guide

Code editors

Work on ASO metadata inside Cursor with Lite ASO

Cursor supports remote Streamable HTTP MCP servers and OAuth, using the same mcp.json configuration in the editor and Cursor Agent CLI.

Official Cursor documentation

What you can do

Compare keyword gaps with repository metadata

Let Cursor retrieve keyword and competitor observations for the target storefront, then compare them with the store copy tracked in your repository. Request a reviewable patch and keep publication outside the automated step.

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

    Add the configuration to .cursor/mcp.json for one project or ~/.cursor/mcp.json for all projects, then reload Cursor or enable lite-aso from MCP settings.

    ~/.cursor/mcp.json
    {
  "mcpServers": {
    "lite-aso": {
      "url": "https://mcp.liteaso.com/mcp"
    }
  }
}

    Cursor documents Streamable HTTP and OAuth support without naming LiteASO's protocol revision. Keep Cursor current and test a read tool first.

  2. Authorize your connection

    When Cursor marks the server as requiring authentication, complete its OAuth flow. Cursor Agent users can start the same flow with the login command.

    Command / client console
    agent mcp login lite-aso

  3. Check the connection

    Open Cursor's Available Tools and confirm LiteASO tools are enabled. Cursor Agent users can also list servers and authentication status from the terminal.

    Command / client console
    agent mcp list

  4. Try your first ASO task

    Paste this starting prompt into Cursor, 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 find keyword gaps for this app, then inspect the repository's store metadata files and propose a reviewable patch without publishing it.

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

Should Lite ASO go in the project or global Cursor config?

Use .cursor/mcp.json when the connection belongs to one project and ~/.cursor/mcp.json when you want it across projects. Reload Cursor after editing the file and confirm Lite ASO appears in Available Tools.

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.