Node.js/TypeScript MCP server for Atlassian Confluence. Provides tools enabling AI systems (LLMs) to list/get spaces & pages (content
Nothing to run from here
Eurorack is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
17
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Citation-anchored Eurorack module reference: specs, compatibility, and patch techniques.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http eurorack-mcp https://eurorackref.com/mcp
# 2 — ask your agent for something these tools do
# get_module, get_modules, visualize_module and 14 more
Eurorack costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ECAll 1 server
eurorackref.com1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http eurorack-mcp https://eurorackref.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Return the full citation-anchored specification for one Eurorack module by id. Use this when the user names a specific module and you want its specs (HP, power, jacks, parameters), capabilities (envelope, quantizer, logic, etc.), or firmware history. The typed prose fields (jack/parameter/mode descriptions) are paraphrased summaries; manual_outline → get_manual_chunk give the verbatim manual pro
| Parameter | Type | Required | Notes |
|---|---|---|---|
| module_id | string | yes | Stable module id, "<manufacturer-id>/<module-slug>" (e.g. "alm-busy-circuits/pamelas-new-workout"). |
| view | string | no | Optional: "concise" returns the id-card subset (name, manufacturer, hp, description, capabilities, production_status, replaced_by) and drops the heavy arrays — good for triage or multi-module sweeps. |
| fields | array | no | Optional: top-level keys to include (e.g. ["jacks","parameters"]) when you only need a slice and want to skip the full payload. Omit for everything. id and _meta are always returned. Takes precedence |
| heading_filter | string | no | Optional: case-insensitive substring matched against manual_outline heading_path. Narrows the outline to chunks under a heading (e.g. "calibration") so you skip scanning a long outline. |
| outline_offset | integer | no | Optional: zero-based offset into the (optionally heading-filtered) manual_outline. Page past the default cap instead of falling back to search_manual. |
| outline_limit | integer | no | Optional: max manual_outline entries to return this call (default 100, hard max 250). |
Batched get_module — returns { modules: [...], errors: [...] } with full citation-anchored specs for up to 25 modules in one call. Prefer this over multiple get_module calls when you have a known list of modules to fetch (e.g. preparing to call draw_patch_diagram across N modules, comparing several candidates side-by-side). One round trip vs. N. Args: - module_ids: array of "<manufacturer-id
| Parameter | Type | Required | Notes |
|---|---|---|---|
| module_ids | array | yes | — |
| view | string | no | Optional: "concise" returns the id-card subset for every module in the batch and drops the heavy arrays — cheapest way to triage a list. "full" (default) returns complete specs. Ignored when fields |
| fields | array | no | Optional: top-level keys to include on every module in the batch (e.g. ["jacks","parameters"]) when you only need a slice — keeps a multi-module fetch from returning full specs. Omit for everything. i |
| heading_filter | string | no | Optional: case-insensitive substring matched against manual_outline heading_path, applied to every module in the batch. |
| outline_offset | integer | no | Optional: zero-based manual_outline offset, applied to every module in the batch. |
| outline_limit | integer | no | Optional: max manual_outline entries per module (default 100, hard max 250). |
Module visualization tool. Use when the user wants to understand how a module's modes work, how parameters change between modes, or what a specific mode does — a visualization communicates the per-mode behavior better than prose. The host renders the result inline in the chat as an interactive visualization (mode buttons, per-mode descriptions, schematic curves); you do not need to build an artifa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| module_id | string | yes | Stable module id, "<manufacturer-id>/<module-slug>" (e.g. "whimsical-raps/three-sisters"). |
Search the corpus for Eurorack modules matching a combination of filters. Filters compose with AND. Omit any filter to leave that dimension unrestricted. The result is sorted by module name; pagination metadata in the response envelope lets you page through long result sets. Args: - capability (string): capability id, e.g. 'envelope-generator', 'clock-source'. Run a search with NO capability
| Parameter | Type | Required | Notes |
|---|---|---|---|
| capability | string | no | Capability id (kebab-case). |
| manufacturer | string | no | Manufacturer id. |
| hp_min | integer | no | — |
| hp_max | integer | no | — |
| signal_type_in | string | no | — |
| signal_type_out | string | no | — |
| text | string | no | — |
| voct_tracking_range_min | number | no | — |
| voct_tracking_quality | string | no | — |
| voct_temperature_compensated | boolean | no | — |
| audio_outputs_min | integer | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
Bulk fuzzy name → id resolver. Pass a list of module NAMES (the way a user writes their rack — "Maths", "Plaits", "Pamela's New Workout", "Morph 4") and get back, per name, the best-matching corpus module id plus recovery affordances. This is the "import my rack" tool: resolving a 60-module inventory is ONE call here, not 60 search_modules calls. Use this the moment a user gives you a list of mod
| Parameter | Type | Required | Notes |
|---|---|---|---|
| names | array | yes | Module names (or ids) to resolve, up to 100. Order and duplicates preserved. |
Full-text search across parsed module manuals, product pages, and firmware release notes. Use this only when the question is about content that lives in continuous prose rather than in typed fields: - Procedural: calibration sequences, button combos, factory-reset steps, save/load procedures. - Diagnostic: LED color meanings, error indicators, troubleshooting trees. - Firmware specifics bey
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search terms. |
| module_id | string | no | — |
| source_id | integer | no | — |
| source_type | string | no | — |
| limit | integer | no | — |
Read one manual chunk by id to ground your answer in the manufacturer's documentation — the drill-in partner to get_module's manual_outline. Use it when a claim (voltage range, behavior, calibration step) benefits from the source's own account. Read the chunk, then answer in your own words and point the user to the source (audit_url) to verify. Paraphrase the substance; do not paste the chunk
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chunk_id | integer | yes | Chunk id from manual_outline[].chunk_id or a search_manual result. |
Return modules that have a typed compatibility relationship with the given module. Both edge directions are returned and tagged via the per-match direction field — so a single call answers both "what is X a R for?" and "what is a R for X?". relationship is OPTIONAL. Omit it to get EVERY edge touching the module across all relationship kinds — the bare "what pairs with / relates to X?" questio
| Parameter | Type | Required | Notes |
|---|---|---|---|
| module_id | string | yes | — |
| relationship | string | no | — |
| limit | integer | no | — |
Given a rack (a set of module ids the user owns), rank the modules NOT in the rack by how many rack members they pair with. The set-level companion to find_compatible_with: where that answers "what pairs with module X?", this answers "given my whole rack, what single module should I add — the one that pairs with the most of what I already have?". The ranking signal is pair_count — the number of
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rack | array | yes | — |
| relationship | string | no | — |
| limit | integer | no | — |
Return canonical synthesis / patching techniques with role-keyed module realizations drawn from the corpus. Use this when the user asks "how do I do X?" with X being a recognisable technique (low-pass-gate plucks, pinged-filter percussion, parallel multiband processing, complex-oscillator FM, karplus-strong pluck, clocked-delay feedback, modal-resonator excitation, wavefolder harmonics, envelope-
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filter | object | no | — |
For a (technique_id, role_id) pair, return modules that can fill the role, ranked by affordance match. Use this when the user has named a technique and you need to recommend modules for a specific role within it (e.g., "what should I use for the lpg role in a lowpass-gate-pluck patch?"). Optionally pass available_modules to restrict the search to the user's rack — the tool surfaces both documente
| Parameter | Type | Required | Notes |
|---|---|---|---|
| technique_id | string | yes | — |
| role_id | string | yes | — |
| available_modules | array | no | — |
Given a rack (the module ids the user owns), return which canonical patch techniques the rack can realize, and which it is one module away from. The set-level companion to find_role_realizations: where that answers "which module fills role R in technique T?", this answers the rack owner's actual question — "given everything I own, what can I actually do, and what am I close to?". This is the righ
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rack | array | yes | — |
| limit | integer | no | — |
Call this when the user asks what they can SELL, remove, downsize, or trim — "what can I sell?", "which modules are redundant?", "what's doing double duty?", "I have too many modules, what can go?", "what's not pulling its weight?". The inverse of reachable_techniques: where that adds, this prunes. Given the user's COMPLETE rack, it runs a leave-one-out over the same technique matcher reachable_t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rack | array | yes | — |
Return a canonical definition for a primitive Eurorack / synthesis concept and its relations to other concepts in the corpus. Use this for VOCABULARY questions, not module questions — when the user is asking what a term means or how two terms relate, not which modules implement it. Typical shapes: - "Is four-quadrant mult the same as through-zero AM?" → lookup_concept("four-quadrant mult") -
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
Return provenance metadata for one source by integer source_id. Sources include manufacturer manuals, product pages, firmware notes, schematics, errata, and (in v2) field notes. Source ids are surfaced wherever facts cite their origin — in get_module's reference list, in the audit page citation links, and (in v2) in the claims table. Args: - source_id (integer, required) Returns metadata only
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source_id | integer | yes | — |
Patch diagram tool. Use when the user describes routing across multiple Eurorack corpus modules. Renders modules as boxes laid out by wire topology (matrix-shaped patches anchor on a hub; otherwise modules step left-to-right by signal-flow rank), jacks as colored ports keyed to signal type, wires as bezier curves. Inline SVG on claude.ai surfaces (web, Desktop chat, mobile); JSON elsewhere. (When
| Parameter | Type | Required | Notes |
|---|---|---|---|
| modules | array | yes | — |
| wires | array | yes | — |
| notes | array | no | Optional patch-level prose hints displayed below the graph. |
Report when this MCP server couldn't fully answer a question. Not a query tool — calling this writes a feedback record. Call this proactively — without being asked — whenever you hit one of: - missing_field: a field you expected on a module wasn't present (e.g. "I needed the LFO frequency range on Pamela's New Workout and parameter_zones didn't have it"). - missing_module: a module the user a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | — |
| module_id | string | no | — |
| tool_name | string | no | — |
| expected | string | yes | — |
| observed | string | yes | — |
| suggestion | string | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Eurorack or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.16.0.
0.16.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Eurorack can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.