Skip to main content
Lite ASO
Browse documentation

MCP setup guide

Code editors

Use Lite ASO with GitHub Copilot in VS Code

VS Code accepts remote HTTP MCP servers in mcp.json and can authorize them through its MCP authentication flow.

Official VS Code documentation

What you can do

Check store copy against current keyword observations

Ask the Copilot agent to retrieve Lite ASO observations for one market and compare them with the store-copy constants in the workspace. Keep the proposed text as a reviewable change with its source context attached.

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

    Create .vscode/mcp.json with the server block for a shared workspace connection, or run MCP: Add Server and choose HTTP plus a user-level target for a private global setup.

    .vscode/mcp.json
    {
  "servers": {
    "lite-aso": {
      "type": "http",
      "url": "https://mcp.liteaso.com/mcp"
    }
  }
}

    MCP behavior can differ between the extension host and Agent Host. VS Code documents forwarding rules, but not a LiteASO protocol-version certification.

  2. Authorize your connection

    Start the LiteASO server from the MCP view and follow the VS Code authentication prompt. Approve workspace trust only after reviewing the server URL and tools.

  3. Check the connection

    Run MCP: List Servers, start lite-aso if needed, and confirm its tools appear in the agent tools picker before sending an ASO request.

  4. Try your first ASO task

    Paste this starting prompt into VS 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 for the strongest keyword opportunities for my primary market, then compare them with the store-copy constants in this workspace.

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 keep the VS Code connection private to my user account?

Yes. Use MCP: Add Server and choose the user-level target instead of committing .vscode/mcp.json. In either case, review the server URL and tools before accepting workspace trust or an MCP action.

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.