NoMac App Store

app.nomacPublished by nomac.appOfficial publisherv1.0.0Updated Oct 27, 2026

Signing, TestFlight, App Store metadata, screenshots and App Review for AI agents, on a NoMac Mac.

The publisher's own server: NoMac

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint that lets an AI assistant handle iOS app signing, TestFlight, App Store metadata, screenshots and App Review on a NoMac Mac.

What you can do
  • Sign apps and manage signing assets for distribution.
  • Distribute builds through TestFlight.
  • Prepare and manage App Store listing metadata.
  • Capture or manage App Store screenshots.
  • Handle App Review steps for submitted apps.
When to use it
Useful when an assistant should help ship an Apple app end to end: preparing signed builds, pushing them to TestFlight, filling in store metadata and screenshots, and moving through App Review without a local Mac.
Requirements
A remote streamable HTTP endpoint at mcp.nomac.app; OAuth authentication is required. No environment variables or headers are declared. The service runs on a hosted NoMac Mac, so no local runtime is needed.
Before you install
OAuth grants the server access to your Apple developer workflow, so review the scopes and account it connects to. The tools can change store listings, distribute builds and submit apps for review, which affects real releases; confirm before any publishing or submission step. No tool list is published, so verify capabilities before relying on it.

Installation

In SourceWeft

  1. Open NoMac App Store in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.nomac%2Fappstore/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "nomac-app-store": {
      "type": "http",
      "url": "https://mcp.nomac.app/appstore"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 19, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Nomac integrations