Skip to main content
Lite ASO
Browse documentation

MCP setup guide

Code editors

Use Lite ASO in Zed's native agent workflow

Zed supports remote MCP servers in context_servers and prompts for standard MCP OAuth when no Authorization header is configured.

Official Zed documentation

What you can do

Map ranking observations to open store metadata files

Ask the Zed Agent to summarize current risks and opportunities for one storefront, then relate them to the metadata files open in the editor. Review the cited observations before accepting any proposed edit.

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

    Open Settings → AI → MCP Servers, choose Add Remote Server, and enter the LiteASO endpoint, or add the shown block to Zed's settings.json.

    settings.json
    {
  "context_servers": {
    "lite-aso": {
      "url": "https://mcp.liteaso.com/mcp"
    }
  }
}

    Zed documents remote MCP and OAuth, but only selected MCP features and no LiteASO protocol guarantee. Keep Zed current and verify the tool list.

  2. Authorize your connection

    Leave the Authorization header unset to let Zed open its standard MCP OAuth flow, then sign in to LiteASO and approve access.

  3. Check the connection

    Return to the MCP Servers settings, confirm lite-aso is connected, and check that its tools are available to the Zed Agent before testing a read.

  4. Try your first ASO task

    Paste this starting prompt into Zed, then replace the app and country with your own. Ask the agent to explain any missing data before continuing.

    Example ASO prompt
    Ask LiteASO to summarize this app's ranking risks and opportunities, then map the findings to the store metadata files open in Zed.

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

How do I make Zed start the Lite ASO OAuth flow?

Configure the remote server without an Authorization header. Zed can then open its standard MCP OAuth flow; after signing in, return to MCP Servers and confirm the connection and tool list.

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.