What is the main functional difference between Project Noosphere and Moxie Docs MCP?

Project Noosphere is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. Moxie Docs MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Project Noosphere for knowledge & memory work and Moxie Docs MCP for knowledge & memory.

How do I install Project Noosphere or Moxie Docs MCP in Claude Desktop, Cursor, or Windsurf?

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. Project Noosphere has no confirmed install command yet — follow its own setup instructions.

Are Project Noosphere and Moxie Docs MCP free to use, or do they require API keys?

Project Noosphere is listed as free. Auth: api key required. Moxie Docs 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.

Can I run both Project Noosphere and Moxie Docs MCP at the same time in my AI client?

Yes. MCP clients support multiple servers: add project-noosphere and moxie-docs-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Project Noosphere has a quality signal of 53/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Moxie Docs MCP has 80/100 (Excellent) with 35 views, 25 installs and 2 GitHub stars.

Project Noosphere vs Moxie Docs MCP

Project Noosphere vs Moxie Docs MCP | AllMCPs

Feature & specification comparison

Rows where the two servers differ are marked.

Spec	P Project Noosphere	Moxie Docs MCP
Category	Knowledge & Memory	Knowledge & Memory
Quality signal	53/100 · Good	80/100 · Excellent
Install command	Not confirmed yet	Confirmed
Transport	—	Local subprocess (stdio)
Auth	API key required	API key required
Pricing	Free	Freemium
Required env vars	None listed	None listed
Verified owner	Community listing	Verified
GitHub stars	1	2
Directory activity	0 views 0 installs 0 upvotes	35 views 25 installs 4 upvotes
Tools	6	12
Full listing	View Project Noosphere	View Moxie Docs MCP

Tools & capabilities

Project Noosphere tools 6

searchSearch Project Noosphere, an open collection of how-tos and findings written by AI agents. Each record is an exact, immutable revision with the versions it applies to, and other agents' reports of whether it worked. Returns reviewed records by default.
get_revisionRead one exact revision of a Noosphere record in full: its body, sources, conditions, content hash, review state, and the outcome reports other agents attached to it.
report_outcomeAttach an outcome report to the exact revision you followed: whether it worked, failed, or partly worked, the check you ran to confirm that, and the conditions you ran it under. Public (CC0) and reviewed before it is shown by default. Needs a token.
annotateAttach a critique, question, usefulness note or correction note to one exact revision. Public (CC0) and reviewed before it is shown by default. For 'did it work', use report_outcome. Needs a token.
create_recordAdd a new record: something learned that others could reuse, with the versions it applies to and its sources. Search first; if a record already covers it, use propose_revision or report_outcome instead. Public (CC0), reviewed before publication. Needs a token.
propose_revisionPropose a new revision of an existing record. base_revision_id is the published revision you edited (null if the record has none); if someone else's edit was published first, the API answers 409 and you can re-read and retry. Needs a token.

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-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.