openisd-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@openisd-mcp Design a closed box with Qtc 0.707 for the Dayton driver ND105-8 of the library"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
openisd-mcp
MCP server (stdio) for the OpenISD Thiele/Small loudspeaker physics engine.
An agent (Claude, opencode, etc.) can:
search_drivers("dayton 10")→ match from 1065+ curated.wdrdriversget_driver→ full T/S parameters with upstream validation issues (errors block, warns only omit a reference line)design_box→ sealed (target Qtc) or vented (QB3/Thiele alignment) with Vb, Fb, port dimensions, EBP suitability advicesimulate→ SPL curve (≈60 points), F3, Qtc/Fc or Fb, max SPL & limiter (Xmax vs power), excursion & impedance peaks; degenerate designs (NaN curves) are rejected before returningevaluate_design→ automated PASS/WARN/FAIL checklist: Qtc/Fb alignment, excursion margin vs Xmax, port velocity/chuffing, F3 extension, SPL limiter, impedance peak, box volume sanityadd_driver→ persist a custom driver to the library (generates .wdr via upstream exporter)
All physics comes from the vendored @openisd/engine + @openisd/winisd (pinned to a commit SHA) — zero reimplementation. The server is stateless: the design lives in the agent's conversation.
Quick start (opencode / Claude Desktop / any MCP client)
{
"mcpServers": {
"openisd-mcp": {
"command": "npx",
"args": ["openisd-mcp"]
}
}
}opencode: opencode.json in project root or ~/.config/opencode/opencode.json
Claude Desktop: claude_desktop_config.json (see below)
Then ask your agent:
"Search for 10-inch Dayton drivers and evaluate a sealed box with Qtc 0.707 for the first one"
Claude Desktop config
// ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
// %APPDATA%\Claude\claude_desktop_config.json (Windows)
{
"mcpServers": {
"openisd-mcp": {
"command": "npx",
"args": ["openisd-mcp"]
}
}
}Related MCP server: SheetsData MCP
Development (vendoring the engine yourself)
git clone https://github.com/OddieDank/openisd-mcp
cd openisd-mcp
npm install
npm run vendor # downloads OpenISD@SHA, compiles, indexes 1065 drivers
npm run build
npm test # golden regression + flow + self-testThe scripts/vendor.sh script documents the SHA, applies one documented patch (winisd's workspace import @openisd/engine → relative), compiles with tsc, and builds the driver search index using upstream's own Driver.fromWdr.
Updating the vendored engine
# Edit OPENISD_SHA to a newer commit from Johnlon/openisd
npm run vendor
npm testArchitecture notes
Vendor commit pinned in
OPENISD_SHA— reproducible, diffable.Engine source is TypeScript with zero deps; compiled to plain JS for runtime stability.
All tools validate at the boundary (zod) before touching the engine.
Engine
Result<T>issues propagate as-is: agent sees{level:'error'}vs{level:'warn'}.classifyFiniteruns on every sweep — a NaN curve never reaches the agent.Self-test at startup mirrors OpenISD's AD-5: golden SPL match (<0.1 dB), vented sweep finite, validation alive.
License
MIT — same as OpenISD.
Available Tools
6 toolsadd_driverA
Add a custom driver to the library. Takes T/S params (friendly units), writes a WinISD-compatible .wdr using upstream's exporter, and makes it searchable immediately. Returns the library file name to use in other tools.
Inputs: Fs (required), Re (required), Vas_l (required), Sd_cm2 (required), +10 more.
design_boxA
Compute an enclosure for a driver: sealed from a target Qtc (default 0.707 Butterworth) or vented from the QB3/Thiele alignment (Vb, Fb, port dimensions). Includes EBP suitability advice. Returns simulateParams ready to pass to simulate.
Inputs: box (required), Fb, ts, Qtc, +3 more.
evaluate_designA
Full design evaluation: runs design_box + simulate + automated PASS/WARN/FAIL checklist in one call. Checks: Qtc/Fb alignment, excursion margin vs Xmax, port velocity/chuffing (Mach ≤5%), F3 extension, SPL limiter, impedance peak, box volume sanity. Returns overall verdict + detailed checks with thresholds. Supports filters for subsonic protection.
Inputs: box (required), Fb, Ql, eg, +9 more.
get_driverA
Load a library driver: full T/S parameters (friendly units) plus upstream validation issues. Warns (e.g. Xmax undefined) do not block — they only omit reference lines.
Inputs: driverName (required).
search_driversA
Search the OpenISD driver library (1600+ woofers/subs, from WinISD .wdr files) by brand/model keywords. Returns matching drivers with key T/S params and the file to use as driverName elsewhere.
Inputs: query (required), limit.
simulateB
Run the OpenISD Thiele-Small engine on a design: SPL curve (~60 points), F3, Qtc/Fc or Fb, max SPL and its limiter (Xmax vs power), excursion and impedance peaks. Degenerate designs (NaN curves) are rejected before returning. Supports HP/LP/Linkwitz/peaking filters for subsonic protection, etc.
Inputs: box (required), Vb_l (required), Fb, Ql, +10 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: searching, loading, designing, simulating, adding, and evaluating. There is no overlap or ambiguity in what each tool does.
Most tools follow a verb_noun pattern (e.g., search_drivers, get_driver, design_box, add_driver, evaluate_design). The single exception is 'simulate', which is a bare verb but still clear and consistent in style.
Six tools cover the core workflow of speaker design (search, load, design, simulate, add, evaluate) without bloat. Each tool earns its place and the set feels well-scoped for the server's purpose.
The surface covers the main lifecycle: discovery, loading, design creation, simulation, custom additions, and full evaluation. Minor gaps exist (e.g., no update or delete for drivers), but these are non-essential and the core domain is well covered.
Related MCP Connectors
Audio for your agent: transcribe, speak, translate, summarise, plus sound effects and music.
Discover, inspect and run 63,000+ agent tools from one balance. Pay per call, no subscriptions.
CC0 sound effects API for AI agents — search, preview, and download via MCP.
Podcast intelligence for agents: transcripts, clips, speaker diarization, mention tracking.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to perform unit-aware engineering calculations with automatic unit conversion, dependency resolution, and access to 500+ units across 75+ categories through the CalcsLive calculation engine.315 npmMIT
- AlicenseAqualityBmaintenanceProvides AI agents with instant, structured access to electronic component datasheets, pinouts, and electrical specifications without requiring PDF uploads. It enables seamless part searching, design validation, and side-by-side component comparisons across major hardware providers.1476 npm12MIT

TiresVote MCPofficial
AlicenseAqualityCmaintenanceEnables agents to search a public tire catalog and professional tire test data — finding tire models, checking their known size variants, comparing 2-4 models, and collecting cited test results — through 12 read-only tools and four workflow prompts over stdio.12MIT- AlicenseAqualityBmaintenanceEnables AI agents to turn natural-language hardware prompts into deterministic schematics and netlists, query live LCSC parts data, validate designs, calculate trace impedance, and estimate PCBA BOM costs through stdio MCP tools and resources.84138 PyPI1MIT