MCP Tools DirectoryAbout this integration
Run an app portfolio across Google Play and the App Store: vitals, reviews, earnings, releases.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.1
- Package
- storepilot
- Last compatibility test
- Not independently tested
Connect your agent
storepilotPublisher documentation and manifest were reviewed without installing the package, supplying store credentials, reading account data, or executing writes. The publisher marks the project early and identifies several live-data and write paths that remain unverified by the publisher. Service-account and App Store Connect key material do not fit one native auth label.
Capabilities: Reads Google Play and App Store Connect portfolio data, Compares cross-store releases, listings, reviews, and app pairings, Previews and confirms supported store-management writes
Connected profiles
Additional details
io.github.sonlenef/storepilot-mcp
Source ↗ · Checked 2026-09-170.1.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17storepilot
Source ↗ · Checked 2026-09-190.1.1
Source ↗ · Checked 2026-09-19MCP client configurations launch the storepilot executable as a local server process.
Source ↗ · Checked 2026-09-19Google Play uses a service-account credential file; App Store Connect uses a private key path, key ID, issuer ID, and optional vendor number.
Source ↗ · Checked 2026-09-19Clients invoke the absolute storepilot executable path and pass only the configured store credentials they use.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19