Skip to main content
Lite ASO
Browse documentation

MCP setup guide

Other clients

Connect another MCP client to Lite ASO

Many MCP clients accept the same server name and endpoint but use different file names, field names, and authentication controls.

Official Generic MCP documentation

What you can do

Start with a scoped, read-only ASO review

After connecting a compatible client, list the apps available to the authorized account and choose one storefront. Request a short review of keyword, listing, or review observations with source scope and missing data clearly stated.

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

    Use your client's remote or Streamable HTTP setup screen and enter the LiteASO endpoint. Treat the JSON block as a shape to translate, not a universal schema.

    JSON
    {
  "mcpServers": {
    "lite-aso": {
      "type": "http",
      "url": "https://mcp.liteaso.com/mcp"
    }
  }
}

    A generic configuration cannot prove compatibility. The client must support remote Streamable HTTP, LiteASO authentication, and protocol 2026-07-28.

  2. Authorize your connection

    Prefer the client's standard MCP OAuth flow. If it cannot complete OAuth, generate a LiteASO agent key and send it as a Bearer token only through the client's documented secret mechanism.

  3. Check the connection

    Confirm the server exposes LiteASO tools, then run one read-only request such as listing your apps. Do not enable automatic write approval during setup.

  4. Try your first ASO task

    Paste this starting prompt into Generic MCP, 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 summarize my app's current ASO health, cite the available store and tracking evidence, and suggest the next three checks.

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

Can I copy the generic JSON into any MCP client?

No. Treat it as a connection example and translate the server, transport, and authentication fields to your client's documented schema. Confirm support for remote Streamable HTTP and protocol 2026-07-28 before relying on the connection.

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.