Skip to main content
Lite ASO
Browse documentation

MCP setup guide

Code editors

Use Lite ASO tools in Windsurf Cascade

Windsurf's documented Cascade configuration accepts remote HTTP servers in mcp_config.json through a serverUrl or url field.

Official Windsurf documentation

What you can do

Review competitor changes beside your app project

Use Cascade to inspect dated competitor metadata observations from Lite ASO while the relevant app project is open. Ask it to separate recorded changes from possible ranking correlations before proposing a next check.

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

    In the Cascade panel, open Actions → MCPs → Open MCP config file, add the LiteASO entry under mcpServers, save, and enable the server from the MCP list.

    mcp_config.json
    {
  "mcpServers": {
    "lite-aso": {
      "serverUrl": "https://mcp.liteaso.com/mcp"
    }
  }
}

    The current Windsurf documentation labels this file flow as legacy Cascade; new tabs default to Devin Local and may use a different configuration surface.

  2. Authorize your connection

    If the client offers OAuth for the remote server, complete the LiteASO browser consent flow. For a header-based setup, use a LiteASO agent key and the client's secret interpolation support.

  3. Check the connection

    Return to Cascade's MCP list and confirm LiteASO is enabled and its tools are counted. Test one read-only request before approving broader actions.

  4. Try your first ASO task

    Paste this starting prompt into Windsurf, 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 identify competitor metadata changes that coincide with ranking movement, and label correlation separately from confirmed 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 can I not find the Cascade MCP config in a new Windsurf tab?

Windsurf marks the documented mcp_config.json flow as legacy Cascade, while new tabs may open Devin Local. Check which surface you are using and follow its current MCP settings instead of assuming the same configuration file applies.

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.