Grandorgue MCP server
GrandOrgue pipe organ simulator MCP server - MIDI bridge, organ control, sample set management, m...
4 stars
Reviews
Write oneNobody has reviewed Grandorgue yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Grandorgue tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 6 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Grandorgue compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,243 servers
- GitHub stars
- 4
- more than 82% of 28,706 servers
Install Grandorgue in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Grandorgue repository's README, as published. We do not edit it. Read it on GitHub
GrandOrgue MCP
Modern Organ Console — a free control surface for the GrandOrgue pipe organ simulator.
GrandOrgue MCP gives GrandOrgue a beautiful, responsive web console + AI-agent-capable backend. It connects to GrandOrgue via MIDI and replaces its aging wxWidgets GUI with a modern React dashboard. Every stop, piston, manual, and swell pedal is controllable from any browser — or from an AI agent via MCP tools.
Built for the GrandOrgue community with gratitude for decades of free organ simulation. This is our contribution back — a modern console layer that works with any existing GrandOrgue installation and sample set.
Contents
- Quick Start
- Documentation
- README.md — this file, overview and quick start
- docs/GRANDORGUE_GUIDE.md — what GrandOrgue is, history of PC organ simulation, Hauptwerk comparison
- docs/ARCHITECTURE.md — system architecture, MIDI bridge, port layout
- docs/BACH_CATALOG.md — complete J.S. Bach organ MIDI repertoire
- docs/MIDI_SETUP.md — step-by-step MIDI configuration
- docs/MCP_TOOLS.md — AI agent tool reference
- docs/SAMPLE_SETS.md — marketplace, free sample sets, installation guide
- Ports
- Tech Stack
- License
Quick Start
Prerequisites
- GrandOrgue installed (Windows / Linux / macOS)
- uv for Python dependency management
- Node.js 20+ for the web console
One-Command Setup
# Install backend deps
just install
# Install frontend deps
just install-web
# Launch everything (backend + frontend + browser)
just webThe backend starts on port 11010 (HTTP mode), the frontend on port 11011.
Claude Desktop (stdio)
The server defaults to stdio transport for MCP clients. Build the bundle with just mcpb and install dist/grandorgue-mcp-vX.Y.Z.mcpb in Claude Desktop. The webapp uses HTTP mode (MCP_TRANSPORT=http), which just web sets automatically.
Manual Start
# Terminal 1 — Backend
uv run grandorgue-mcp
# Terminal 2 — Frontend (opens browser)
cd web_sota && bun run devFirst-Time Setup
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grandorgue: common questions
- Is Grandorgue MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Grandorgue safety report
- Does Grandorgue need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Grandorgue maintained?
- The last commit was 13 days ago (2026-10-24). The latest release is v0.3.0.
- How does Grandorgue compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,243 servers); github stars 4 (more than 82% of 28,706 servers). Full comparison.