Moxie Docs MCP vs Sonovault MCP
A side-by-side look at the Moxie Docs MCP and Sonovault MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Moxie Docs MCP for knowledge & memory work; choose Sonovault MCP for art & culture as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Moxie Docs MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- Its auth model fits you: OAuth 2.0.
- You want tools like
moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.
Choose Sonovault MCP when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SONOVAULT_API_KEY. - You want tools like
search_tracks, lookup_isrc, get_track.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Art & Culture |
| Quality signal | 76/100 · Great | 63/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | OAuth 2.0 | API key required |
| Pricing | Freemium | Freemium |
| Required env vars | None listed | SONOVAULT_API_KEY |
| Verified owner | Verified | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 38 views 25 installs 4 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 12 | 9 |
| Full listing | View Moxie Docs MCP | View Sonovault MCP |
Tools & capabilities
Moxie Docs MCP tools 12
moxie.get_ai_contextCompact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.moxie.get_doc_impactGiven the paths you're about to change (and any you're deleting), returns the conventions, gaps, and existing docs whose evidence overlaps them - and flags net-new/undocumented surfaces.moxie.get_api_contextGiven paths you're about to touch, returns structured context for any API endpoints they map to: method, path, schema, and known consumers/features.moxie.review_changeSelf-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docs, undocumented surface, and broken references.moxie.get_conventionsDiscovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.moxie.search_docsSemantic + keyword search over generated docs, conventions, gaps, and AI context.moxie.get_doc_gapsUnresolved documentation gaps with severity and the paths they concern.moxie.get_documentation_opportunitiesRecommended doc work: missing docs, drift repairs, and PR templates.moxie.get_documentation_patternsHow the repository organizes and maintains its docs (where new docs belong).moxie.list_docsPaginated, section-grouped table of contents of every generated doc.moxie.propose_doc_updateAdd or update a doc as part of your current change; returns the target path + Markdown to write into your branch.moxie.propose_doc_removalRemove a Moxie Docs-tracked doc your change makes obsolete; returns the path to delete in your branch.
Sonovault MCP tools 9
search_tracksFuzzy search by artist + title. Returns ISRC, genre, label, release date.lookup_isrcExact recording lookup by ISRC.get_trackFetch a track by SonoVault ID.get_work_codesRecording to composition: the ISWC(s) behind a recording.get_recordings_of_workComposition to recordings: every recording of an ISWC.get_platform_linksOne track's ID and deep link on all 7 platforms, from any ID or ISRC.resolve_tracksBulk resolve up to 100 track names, ISRCs, or platform IDs.list_genresThe canonical genre hierarchy.browse_tracksDiscover by label, artist, genre, or year (paid tier).
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Moxie Docs MCP
No confirmed install command for Moxie Docs MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Sonovault MCP
{
"mcpServers": {
"rekordcloud-sonovault-mcp": {
"command": "npx",
"args": [
"-y",
"sonovault-mcp"
],
"env": {
"SONOVAULT_API_KEY": "YOUR_SONOVAULT_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Moxie Docs MCP is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. Sonovault MCP belongs to Art & Culture and uses a local stdio subprocess. Pick Moxie Docs MCP for knowledge & memory work and Sonovault MCP for art & culture.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Moxie Docs MCP has no confirmed install command yet — follow its own setup instructions.
Moxie Docs MCP is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. Sonovault MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add moxie-docs-mcp and rekordcloud-sonovault-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Moxie Docs MCP has a quality signal of 76/100 (Great) with 38 views, 25 installs and 2 GitHub stars. Sonovault MCP has 63/100 (Good) with 4 views, 0 installs and 0 GitHub stars.