Skip to main content
Lite ASO
Browse documentation

MCP setup guide

Code editors

Run review-first ASO tasks with Cline

Cline supports hosted Streamable HTTP servers through its Remote Servers UI or MCP settings JSON, including custom authorization headers.

Official Cline documentation

What you can do

Prepare a keyword experiment brief before editing files

Have Cline review the tracked keyword observations available through Lite ASO and prepare a small metadata experiment brief. Require it to show the supporting data and wait for your review before changing repository files.

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

    Generate an agent key from LiteASO's Connect page, replace the placeholder in the configuration, then add the block through Cline's MCP Servers → Configure screen.

    JSON
    {
  "mcpServers": {
    "lite-aso": {
      "type": "streamableHttp",
      "url": "https://mcp.liteaso.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_LITEASO_API_KEY"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

    Cline's public guide documents remote HTTP plus headers, not LiteASO OAuth or the required protocol revision. This guide therefore uses the supported agent-key path.

  2. Authorize your connection

    The documented Cline path uses an Authorization header for this setup. Keep the key out of source control, never paste it into prompts, and rotate it from LiteASO if exposed.

  3. Check the connection

    Open Cline's MCP Servers panel, confirm lite-aso is enabled, and check that its tools appear. Start with a read-only app or keyword request.

  4. Try your first ASO task

    Paste this starting prompt into Cline, 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 inspect my tracked keywords and prepare a metadata experiment brief; show the evidence and wait before changing any repository files.

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 this Cline setup use an agent key instead of OAuth?

Cline's documented remote-server path supports custom Authorization headers, so this guide uses a Lite ASO agent key. Store it only through Cline's documented configuration, keep it out of source control, and rotate it if exposed.

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.