Skip to main content
Lite ASO
Browse documentation

MCP setup guide

Terminal agents

Run ASO research from Claude Code with Lite ASO

Claude Code recommends HTTP for hosted MCP servers and can complete an OAuth login after the LiteASO endpoint is registered.

Official Claude Code documentation

What you can do

Explain keyword movement before planning the next change

Have Claude Code review dated keyword observations for one storefront and separate recorded movement from interpretation. Use the result to prepare a small next-step checklist inside the project you already have open.

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

    Run the add command once. The user scope makes LiteASO available across your Claude Code projects; omit the scope flag if you only want a local project entry.

    Terminal
    claude mcp add --transport http --scope user lite-aso "https://mcp.liteaso.com/mcp"

    Use a current Claude Code release. Anthropic documents Streamable HTTP and OAuth behavior, but does not certify LiteASO's required protocol version.

  2. Authorize your connection

    Run the login command or open /mcp inside Claude Code, select lite-aso, and complete the browser sign-in. Claude Code refreshes stored OAuth tokens when supported.

    Command / client console
    claude mcp login lite-aso

  3. Check the connection

    Inspect lite-aso with the get command. A healthy server appears connected; /mcp provides the same status and lets you review its tools.

    Command / client console
    claude mcp get lite-aso

  4. Try your first ASO task

    Paste this starting prompt into Claude Code, 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 explain the last 30 days of ranking movement for my priority keywords and separate observed evidence from recommendations.

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

Should I add Lite ASO at user or project scope?

Use user scope when you want the connection available across Claude Code projects. Leave out the scope flag for a project-only entry, then open /mcp in that project to confirm the expected server is active.

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.