Stora in your terminal.
An open-source CLI and MCP server that brings App Store automation to Claude Code, Cursor, and any MCP-compatible client. Capture screenshots, scan compliance, and manage your pipeline from the command line.
Everything you need. Nothing you don't.
CLI
stora screenshots, stora compliance, stora doctor. Full App Store automation from your terminal with a single npm install.
MCP Server
Open-source MCP server with 10 tools for App Store automation. Works with Claude Code, Cursor, Windsurf, and any MCP client.
Open source
MIT licensed. Modular packages: @stora/screenshots, @stora/compliance, @stora/shared. Contribute on GitHub.
API access
Programmatic access to all Stora capabilities. Build custom integrations and workflows on top of the platform.
From install to running a release in four commands.
- 01
npm i -g stora-sh
Installs the CLI globally. Node 20+ required. Zero other deps.
- 02
stora login
Opens your browser for OAuth. Token lives in the OS keychain — never in dotfiles.
- 03
stora link
Detects your repo and links it to a Stora project. Picks up bundle ID, platform, and target SDK automatically.
- 04
stora release ship
Runs the full pipeline: compliance → screenshots → ASO → submit. Same pipeline the web app runs, just headless.
Designed for agents first, humans second.
The Stora MCP server exposes 10 tools — create_release, run_compliance_scan, capture_screenshots, draft_aso, submit_to_app_store, and others — that any MCP-compatible agent can invoke. Claude Code, Cursor, Windsurf, Zed agents, and homemade agents all work the same way. Point them at the MCP server, hand them a project ID, and they can ship releases without ever touching a browser.
Every tool call through MCP returns structured data: finding lists from a compliance scan, device × locale matrix from a screenshot run, keyword recommendations from an ASO draft. Agents can reason about the output programmatically rather than scraping HTML or dashboard pixels.
The CLI ships from the same package set as the MCP server — the tools share a codebase. If you build something with one, you can trivially wire it into the other. A script that works locally can become an agent tool with a three-line MCP wrapper.
Who lives in the terminal.
Frequently asked.
- Where's the code?
- github.com/storasource — main repos are stora-cli, stora-mcp-server, and the individual @stora/* task packages. All MIT. Contribution guide in each.
- Does the CLI work without a Stora account?
- No — we don't run un-authenticated scans because compliance rules include Stora-proprietary research. Everything else (screenshots, ASO) pulls from store APIs with your credentials, so an account is required for attribution.
- Can I use the MCP server with my own LLM?
- Yes — any MCP-compatible client works, including self-hosted agents. The server is a standalone Node process that speaks MCP over stdio or HTTP.
- How do I extend it?
- Fork the MCP server, add a tool following the pattern in tools/ (name, input schema, handler), publish it as an npm package. The CLI picks up registered tools automatically via the plugin entry-point.
Ready to ship?
Connect your GitHub repo and let agents handle the rest. Your next release, out the door in minutes.