Noetive vs Moxie Docs MCP
A side-by-side look at the Noetive and Moxie Docs MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Noetive for knowledge & memory work as a local process; choose Moxie Docs MCP for knowledge & memory. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Noetive when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
NOETIVE_KEY_SECRET. - You want tools like
noetive_publish, noetive_search, noetive_subscribe.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 57/100 · Good | 76/100 · Great |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | OAuth 2.0 |
| Pricing | BYOK (pay the provider) | Freemium |
| Required env vars | NOETIVE_KEY_SECRET | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 2 | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 40 views 25 installs 4 upvotes |
| Tools | 5 | 12 |
| Full listing | View Noetive | View Moxie Docs MCP |
Tools & capabilities
Noetive tools 5
noetive_publishPublish a message so peers can find it by meaningnoetive_searchSearch a namespace with SemQL and read the matching messagesnoetive_subscribeWatch a namespace for live matches for a bounded windownoetive_lintCheck a SemQL query before running itnoetive_healthCheck that the editor can reach Noetive and its key is accepted
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.
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.
Noetive
{
"mcpServers": {
"noetive": {
"command": "npx",
"args": [
"-y",
"@noetive/mcp-server"
],
"env": {
"NOETIVE_KEY_SECRET": "YOUR_NOETIVE_KEY_SECRET_HERE"
}
}
}
}
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.
Frequently asked questions
Noetive is categorized under Knowledge & Memory and uses a local stdio subprocess. Moxie Docs MCP belongs to Knowledge & Memory and uses an install path we have not confirmed yet. Pick Noetive for knowledge & memory work and Moxie Docs MCP for knowledge & memory.
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.
Noetive is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Moxie Docs MCP is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. 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 noetive and moxie-docs-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Noetive has a quality signal of 57/100 (Good) with 0 views, 0 installs and 2 GitHub stars. Moxie Docs MCP has 76/100 (Great) with 40 views, 25 installs and 2 GitHub stars.