mcpbeat Sign in

Heimdall MCP Server

by erayendes Your server? Claim it
local only

Heimdall runs on your own machine — the client starts it, so there is no endpoint to ping. 513 installs a week from npm. Last commit 26 Oct 2026.

Every App Store Connect + StoreKit 2 endpoint. 929 tools in 13 profiles, narrow to 27.

Installs per day peak 762 · avg 110 · -44% w/w
a month agotoday
513
Installs / week
npm · @erayendes/asc-mcp
56
Stars
10 open issues
26 Oct 2026
Last commit
27 releases in 90 days
MIT
License
TypeScript

What the code does

We read the source, 4 d ago · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

        const rows = JSON.parse(execFileSync(t.bin, t.list, { encoding: 'utf8' })) as unknown;

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add asc-mcp -- npx -y @erayendes/asc-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "asc-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@erayendes/asc-mcp"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.asc-mcp]
command = "npx"
args = ["-y", "@erayendes/asc-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "asc-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@erayendes/asc-mcp"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "asc-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@erayendes/asc-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: ASC_KEY_ID (App Store Connect API Key ID. Normally written for you by `npx -y @erayendes/asc-mcp setup`), ASC_ISSUER_ID (App Store Connect Issuer ID (a UUID). Normally written for you by `setup`), ASC_PRIVATE_KEY (The .p8 private key as PEM text. Prefer `setup`, which stores it in the macOS Keychain instead of any config file; set this only where a Keychain is unavailable, such as CI), ASC_PRIVATE_KEY_PATH (Path to the .p8 file, as an alternative to pasting its contents. Off macOS this is what `setup` records), ASC_BUNDLE_ID (Bundle ID of one app. Only needed by the StoreKit 2 transaction tools on the monetization profile).

Alternatives to Heimdall

same job, measured the same way
0bridge
by 0bridge

Every service you connect, one MCP endpoint for all your AI tools. Sign in once.

answering
App Store Connect MCP
by abd3lraouf-studios

App Store Connect + StoreKit 2: 1,293 Apple operations behind 11 tools, writes confirmed.

72 installs/wk local only
NoMac (all tools)
by nomac

Everything NoMac in one server: the Mac, the cloud iPhone and the App Store.

answering
Google Search Console
by mamrrez

Google Search Console: 37 tools, every API endpoint, hourly data, history beyond 16 months.

145 installs/wk local only
App Store data for agents
by fetcher-appstore

9 App Store endpoints. Pay per call in USDC via x402.

11 tools answering
Ruby Native
by ruby-native

Ship a Rails app to the App Store and Google Play. Every ruby_native command as a tool.

local only
App Store Connect MCP
by gjeltep

Interact with Apple's App Store Connect API

141 installs/wk local only
Octri API Docs
by octri

Search an Octri project's API docs and call its endpoints as tools, shaped by its SDK Studio config.

710 installs/wk local only

Heimdall — questions

Answers built from our own checks of this server.

Why is there no uptime for Heimdall?
Heimdall runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @erayendes/asc-mcp was installed 513 times last week.
How do I connect Heimdall?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls @erayendes/asc-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use Heimdall?
The npm package @erayendes/asc-mcp was installed 513 times in the last week. Week over week that is -44%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Heimdall open source?
Yes — it is published under the MIT licence, written in TypeScript, 56 stars on GitHub and 10 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.