Skip to main content
Lite ASO
Browse documentation

MCP setup guide

Terminal agents

Use Lite ASO from OpenCode terminal sessions

OpenCode supports remote MCP entries in opencode.json and automatically starts OAuth when a server returns an authentication challenge.

Official OpenCode documentation

What you can do

Turn ASO observations into a small repository checklist

Ask OpenCode to rank the most relevant keyword and review observations for the selected app and storefront. Then convert those findings into a focused checklist for the repository without treating suggestions as measured outcomes.

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 LiteASO block to your project or global OpenCode configuration. Keep the entry URL-only so OpenCode can use OAuth discovery instead of a hard-coded token.

    opencode.json
    {
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lite-aso": {
      "type": "remote",
      "url": "https://mcp.liteaso.com/mcp"
    }
  }
}

    OpenCode documents automatic OAuth for remote servers, but its docs do not certify LiteASO's protocol version. Use a current release and verify tools.

  2. Authorize your connection

    Run the auth command and finish consent in your browser. OpenCode stores MCP credentials separately from opencode.json and can remove them with mcp logout.

    Command / client console
    opencode mcp auth lite-aso

  3. Check the connection

    List MCP servers and confirm lite-aso is connected. If discovery fails, use opencode mcp debug lite-aso before changing the configuration.

    Command / client console
    opencode mcp list

  4. Try your first ASO task

    Paste this starting prompt into OpenCode, 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 rank this app's most actionable keyword and review opportunities, then produce a small implementation checklist for the current repository.

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

Does OpenCode store Lite ASO credentials in opencode.json?

OpenCode stores MCP OAuth credentials separately from opencode.json when you use the URL-only remote configuration. Use opencode mcp logout to remove them, and avoid adding a hard-coded token to the project file.

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.