Metarun

What metarun MCP server does

The metarun MCP server brings selected App Store Connect work into an IDE-based workflow. The supplied listing identifies five areas it covers: pricing, listings, screenshots, releases, and AI visibility. This makes it relevant to developers who manage an app’s store presence and release process while working in an editor or other IDE environment.

The server’s scope is App Store Connect rather than general-purpose development tooling. Its purpose is to provide an MCP-based way to work with app-store data and release-related tasks through an AI-compatible development workflow. The available material does not describe additional services, repositories, build systems, analytics products, or source-control integrations.

How it works

The metarun MCP server is presented as an MCP server that runs App Store Connect operations from an IDE. In practical terms, an MCP-compatible client can use the server as the connection point for the listed App Store Connect areas. The source description does not specify whether actions are exposed as individual tools, resources, prompts, or another MCP primitive, so implementation details should be confirmed from the project documentation.

Its intended workflow is centered on performing or assisting with App Store Connect tasks without moving to a separate interface for every operation. The listing does not explain authentication, permission scopes, response formats, or whether operations are read-only or mutating.

Tools and capabilities

The documented capability areas are:

• Managing app pricing.
• Working with App Store listings.
• Handling screenshots.
• Managing releases.
• Working with AI visibility.

These categories describe the available scope at a high level. They do not establish specific tool names, parameters, supported platforms, bulk-operation behavior, or the exact actions available within each category.

Limitations and notes

The metarun MCP server has no available README in the supplied material. As a result, installation steps, configuration fields, environment variables, authentication requirements, supported MCP transports, and client compatibility cannot be verified here. The source also does not identify a software license.

Before adopting it for an automated release workflow, verify which App Store Connect operations it can perform, what credentials it requires, and how it handles permissions for pricing, metadata, screenshots, releases, and AI visibility. Client-specific support should also be checked against the project’s current documentation rather than assumed from the IDE-focused description.