MCP setup guide
Chat assistants
Bring Lite ASO research into ChatGPT
ChatGPT can connect to remote MCP servers through custom apps in developer mode, subject to your plan and workspace permissions.
Official ChatGPT documentationWhat you can do
Build an evidence-linked store listing brief
Use the Lite ASO app to review title, subtitle, and tracked keyword observations for a chosen storefront. Ask ChatGPT to organize the findings into a prioritized brief with the supporting data and open questions kept visible.
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
Enable developer mode, open Settings or Workspace settings → Apps → Create, enter the LiteASO MCP endpoint and metadata, then choose the offered authentication method and scan tools.
Full MCP availability and who may create or publish apps depend on the ChatGPT plan and workspace policy. Agent mode does not use custom apps.
Check the connection
Open a new chat, select the LiteASO draft app from the tools menu, and make a read request. Confirm the expected LiteASO tool appears before approving the call.
Try your first ASO task
Paste this starting prompt into ChatGPT, then replace the app and country with your own. Ask the agent to explain any missing data before continuing.
Example ASO promptUse LiteASO to audit my current title, subtitle, and tracked keyword coverage, then return a prioritized brief with evidence and unresolved gaps.
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
Why is the Lite ASO custom app missing in ChatGPT?
Custom app access depends on your ChatGPT plan, developer mode, and workspace policy. Confirm the app is published or available as a draft to your account, and use a regular chat because agent mode does not use custom apps.
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.