MCP Protocol

AI Integrations

Lite ASO exposes authorized ASO observations and scoped tools through the Model Context Protocol. Compatible assistants can inspect dated keyword and competitor data, prepare metadata drafts, and explain deterministic evidence with its coverage and limitations.

How MCP works with Lite ASO

1. Sign up for Lite ASO and add your apps

2. Configure the MCP server connection in your AI assistant (Codex, Claude, or any MCP-compatible tool)

3. Ask the assistant to inspect authorized observations; write actions remain scope-limited and may require an exact-payload approval

Codex

MCP Support

Connect Codex to inspect authorized, timestamped Lite ASO observations and prepare keyword or metadata candidates for review.

Keyword research and suggestions
Editable metadata drafts checked against published limits
Competitor comparisons with storefront and date context
Review-theme summaries when review coverage is available

Learn more

Claude

Native MCP

On Claude surfaces that support custom MCP connectors, inspect scoped Lite ASO observations, reason over their evidence, and prepare drafts without treating estimates as store facts.

MCP tool access on supported Claude surfaces
Approval-gated keyword tracking changes
Evidence-labelled diagnostics and limitations
Dated competitor observations, not continuous surveillance

Learn more

Gemini CLI

CLI Integration

Where the Gemini CLI version supports remote MCP and OAuth discovery, authorize scoped access and inspect Lite ASO observations from the terminal.

Dynamic OAuth via terminal
Interactive agent session
Keyword research and tracking
Metadata drafts for review; no direct store publishing

Learn more

Any MCP-Compatible Agent

Lite ASO uses MCP, but client support differs. A compatible client can request only the tools and data authorized by its scopes; sensitive writes may require approval and Lite ASO does not publish listings directly to a store.

Get Started Free