claude-plugins MCP server
Commit Nov 7, 2026Extends Claude Code with specialized tools for project retrieval, NotebookLM automation, MIDI/OSC bridging, and hardware widget development.
Also known as roomi-fields/claude-plugins
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 7, 2026
- License
- MIT
What is claude-plugins MCP?
claude-plugins extends Claude Code with specialized tools for project retrieval, NotebookLM automation, MIDI/OSC bridging, and hardware widget development.
Summary generated from the project's README
About claude-plugins MCP server
Extending Claude Code with specialized capabilities for technical research, music production, and hardware development is possible through this collection of plugins. Developers can use these tools to manage complex workflows ranging from deep project retrieval to real-time musical instrument control. The suite includes rtfm for indexing code and documentation, notebooklm for interacting with Google NotebookLM notebooks, osc-bridge for connecting to synthesizers and digital audio workstations, and electra-one for creating custom Lua widgets for the Electra One MIDI controller.
Users install these tools directly within Claude Code using marketplace commands. The rtfm plugin provides surgical context through tools like rtfm_search and rtfm_graph, while the notebooklm plugin enables citation-backed Q&A and content generation. For musicians, osc-bridge offers a way to discover device catalogues and send OSC commands to software like Ableton or hardware like 849 synthesizers. Hardware developers can use electra-one to push Lua code to devices via USB SysEx and manage presets using tools like push_to_device and execute_lua.
What you can do with it
- 1Surgical project context retrievalA developer can search through indexed code, legal documents, or research data to find specific context for a task.
- 2Automated NotebookLM content generationYou can automate the creation of reports, presentations, or audio from your NotebookLM notebooks with citation support.
- 3Remote musical instrument controlControl hardware synthesizers or software like Bitwig and Sonic Pi by sending OSC commands through Claude.
- 4Hardware widget developmentDevelop and test custom Lua widgets for the Electra One MIDI controller by pushing code directly to the device.
Written from the project's README. Every use case is checked against a quote from it.
README
View on GitHubClaude Code plugins by roomi-fields
Open-source plugins to extend Claude Code: RTFM (retrieval), NotebookLM (citation-backed Q&A), osc-bridge (MIDI/OSC for synths & DAWs), electra-one (Electra One widget development).
Quick install
/plugin marketplace add roomi-fields/claude-plugins
/plugin install rtfm@roomi-fields
/plugin install notebooklm@roomi-fields
/plugin install osc-bridge@roomi-fields
/plugin install electra-one@roomi-fields
That's it. Each MCP server registers automatically when its plugin is enabled.
What's inside
rtfm — open retrieval layer
| What | Indexes your projects (code, docs, legal, research, data) and serves surgical context via MCP |
| Why | Augment-style code search, but open source, multi-domain, and extensible |
| Tools | rtfm_search, rtfm_expand, rtfm_context, rtfm_discover, rtfm_books, rtfm_graph, rtfm_sync |
| Source | Pulled from roomi-fields/rtfm — pure-Python, no pip install required |
| Docs | roomi-fields.github.io/rtfm |
notebooklm — Google NotebookLM automation
| What | Citation-backed Q&A from your NotebookLM notebooks, plus full Studio generation (audio, video, infographic, report, presentation, data table) |
| Why | Zero hallucinations from your sources. Multi-account rotation with auto-reauth for batch workloads |
| Tools | Q&A with 5 citation formats, source management, notebook library, content download |
| Source | Pulled from roomi-fields/notebooklm-mcp — mcpServers declared in upstream .claude-plugin/plugin.json |
| Prerequisite | Node.js ≥ 18 (the upstream manifest runs npx -y @roomi-fields/notebooklm-mcp — auto-download on first use) |
osc-bridge — MIDI & OSC bridge for synths and DAWs
| What | A clean, named OSC surface in front of 849 hardware synthesizers (MIDI/SysEx) plus DAW & live-coding targets (Ableton, Bitwig, Reaper, Sonic Pi, SuperCollider, Pure Data, TouchDesigner, VCV Rack) |
| Why | One JSON file per device — no Rust recompile to add a synth. The same OSC surface drives hardware and software, locally or from Claude over MCP |
| Tools | MIDI MCP + OSC MCP: discover the device catalogue, read a device's OSC surface, send OSC to synths and DAWs |
| Source | Pulled from roomi-fields/osc-bridge — mcpServers declared in upstream .claude-plugin/plugin.json |
| Prerequisite | Node.js ≥ 18 (the upstream manifest runs npx -y @roomi-fields/osc-bridge mcp — auto-download on first use) |
| Docs | roomi-fields.github.io/osc-bridge |
electra-one — Electra One MK2/Mini widget development
| What | Develop custom Lua widgets and presets for the Electra One MIDI controller from Claude. Push to the device over USB SysEx, run a live Lua REPL, capture knob/button events, pull presets back into your repo |
| Why | The Electra One Lua extension is powerful but its documentation is scattered (official docs + forum + tribal knowledge). The plugin packages the indexed docs, the empirically-confirmed gotchas, and 20 MCP tools so Claude can iterate on hardware without re-paying the discovery tax |
| Tools | 20 MCP tools: push_to_device, execute_lua (REPL), pull_preset, device_state, subscribe, clear_preset_slot, upload_lua_module, doc-search, schema validation, screenshot, and more |
| Source | Pulled from roomi-fields/electra-one-mcp — Python MCP, runs locally |
| Prerequisite | Python ≥ 3.10 + pip install -r requirements.txt (mcp + mido + python-rtmidi). Works on macOS / Linux / Windows / WSL2 (transparent winmm bridge, no usbipd needed) |
| Docs | roomi-fields.github.io/electra-one-mcp |
How they pair
NotebookLM gives you authoritative answers from your sources. RTFM indexes those answers (via the nblm-answer-v1 JSON schema) so you can query them offline without re-hitting NotebookLM.
Your sources ─┐ ┌─► Claude Code (offline)
├─► NotebookLM ─► /batch-to-vault ─► RTFM ┘
PDFs, URLs ──┘ (FTS5 + embeddings, surgical context)
See the RTFM × NotebookLM integration guide for the full recipe.
Why a marketplace?
- One-line install for users (
/plugin marketplace add ...) - Discoverability in Claude Code's
/pluginDiscover tab - Pure aggregator — every plugin is sourced directly from its own repo via
source: url. No code, no wrapper, no duplicated metadata. Each upstreamplugin.jsonis the single source of truth for its version and configuration - Backed by working open-source projects — RTFM benchmarked on FeatureBench, NotebookLM tested on 1000+ overnight questions, osc-bridge driving 849 declarative device JSONs, electra-one running on a physical MK2 over USB SysEx
Repo layout
claude-plugins/
├── .claude-plugin/marketplace.json # the catalog (only file that matters)
├── PLAYBOOK.md # howto for shipping a quality MCP (code, docs, SEO, growth)
├── README.md
└── LICENSE
That's the whole repo. No plugin code lives here — every plugin is sourced from its own GitHub repo at install time. This keeps the aggregator dependency-free and ensures users always get the upstream manifest.
PLAYBOOK.md— the reusable playbook for building and launching every MCP underroomi-fields: server code quality, packaging, in-repo docs, web docs, communication, and growth. Read it before starting a new MCP.
Versioning
Each plugin pins its version in its upstream .claude-plugin/plugin.json. The marketplace entry stays version-less to avoid drift.
rtfm— version pinned inroomi-fields/rtfm/.claude-plugin/plugin.json. Bump it via the RTFM release pipeline.notebooklm— version pinned inroomi-fields/notebooklm-mcp/.claude-plugin/plugin.json. Discipline is automated upstream vianpm run version:checkin CI.osc-bridge— version pinned inroomi-fields/osc-bridge/.claude-plugin/plugin.json. Bumped on each tagged release.electra-one— version pinned inroomi-fields/electra-one-mcp/.claude-plugin/plugin.json. Bumped on each tagged release.
When any plugin ships a new version, users running auto-update or /plugin marketplace update roomi-fields pick it up automatically — no commit needed in this repo.
Updating descriptions and keywords
The description, keywords, and homepage fields in marketplace.json are surfaced in Claude Code's Discover tab before the plugin is cloned, so they need to live in the catalog. To keep them in sync with upstream:
- Pull the latest
descriptionandkeywordsfrom the upstreamplugin.json - Update the corresponding entry in
.claude-plugin/marketplace.json - Commit + push (no version bump needed for the marketplace itself)
Or just leave them — they don't have to match upstream byte-for-byte; they only need to give Discover-tab users an accurate idea of what they're installing.
License
MIT — same as the underlying projects (osc-bridge is GPL-3.0-or-later upstream).
claude-plugins MCP questions
What is included in the claude-plugins package?
The package contains four main plugins: RTFM for open retrieval, NotebookLM for citation-backed Q&A, osc-bridge for MIDI/OSC hardware control, and electra-one for MIDI controller widget development.
How do I install these plugins?
You can install them using Claude Code commands such as /plugin install rtfm@roomi-fields or by adding the marketplace entry.
Can I use these plugins to control hardware synthesizers?
Yes, the osc-bridge plugin provides an OSC surface to control 849 hardware synthesizers and various DAWs.