
Grandorgue Mcp
io.github.sandraschiPublished by GitHub account sandraschiv0.3.0Updated Oct 24, 2026
GrandOrgue pipe organ simulator MCP server - MIDI bridge, organ control, sample set management, m...
Overview
MCP server that bridges an AI assistant to the GrandOrgue pipe organ simulator over MIDI, letting it control stops, pistons, manuals and swell pedals.
- What you can do
- Control the organ: operate stops, pistons, manuals and swell pedals through MIDI from an AI agent or the bundled web console, replacing the simulator's built-in GUI with a React dashboard.
- When to use it
- Useful if you run the GrandOrgue pipe organ simulator and want an AI agent or a browser-based console to drive its stops and manuals instead of the stock interface.
- Requirements
- Runs locally as a stdio process. Needs GrandOrgue installed, at least one sample set, uv for Python dependencies, and Node.js 20+ for the web console; the optional web mode uses ports 11010 (backend) and 11011 (frontend). GrandOrgue must be configured to use the virtual MIDI ports.
Installation
In SourceWeft
- Open Grandorgue Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
GrandOrgue MCP
[Stars] [License] [CI] [Python] [FastMCP] [MIDI] [Fleet SOTA] [React]
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
The 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
First-Time Setup
- Install GrandOrgue from GitHub Releases
- Install at least one free sample set (see docs/SAMPLE_SETS.md)
- Start the MCP server (
uv run grandorgue-mcp) - Open the web console at http://127.0.0.1:11011
- From the Dashboard, click Start GrandOrgue then Connect MIDI
- GrandOrgue must be configured to use the virtual MIDI ports (see docs/MIDI_SETUP.md)
Ports
Tech Stack
License
MIT — free for the GrandOrgue community, forever.
Source: README.md at commit 0f7af48
Tools
0Version history
1- v0.3.0LatestSep 16, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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
- License10 pts