MCP setup guide
Chat assistants
Use Claude for conversational ASO research
Claude and Claude Desktop can add hosted MCP services from Settings as custom connectors, with authentication handled through the connector flow.
Official Claude documentationWhat you can do
Turn recent reviews into listing message candidates
Ask Claude to group recurring themes in the reviews available through Lite ASO and tie each theme to its supporting examples. Then draft a short set of listing message candidates for you to review and test.
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 ASOhttps://mcp.liteaso.com/mcpAdd Lite ASO
Open Settings → Connectors, choose Add custom connector, name it LiteASO, paste the MCP endpoint, and add it. On Team or Enterprise, an owner may need to configure the organization connector first.
Custom connectors are a beta feature for supported paid Claude plans. Mobile can use connectors already added on web, but cannot add a new one directly.
Check the connection
Start a new conversation, enable LiteASO from Search and tools, and ask Claude to list your apps or tracked keywords. Review the tool call before approving it.
Try your first ASO task
Paste this starting prompt into Claude, then replace the app and country with your own. Ask the agent to explain any missing data before continuing.
Example ASO promptReview my latest app-store reviews with LiteASO, group recurring pain points, and suggest three evidence-backed changes to the listing message.
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 add the Lite ASO connector from Claude mobile?
Claude mobile can use a connector that was already added on the web, but it cannot add a new custom connector directly. Complete setup and authorization on the web first, then enable Lite ASO in the mobile conversation.
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.