What is the key difference between Hipocampo and Moxie Docs MCP?

Hipocampo belongs to the Knowledge & Memory category with cloud HTTP/SSE execution, while Moxie Docs MCP belongs to the Knowledge & Memory category with local stdio execution.

How do I install Hipocampo or Moxie Docs MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Hipocampo and Moxie Docs MCP free or paid?

Hipocampo operates under a Free / Open Source model (No auth required). Moxie Docs MCP operates under a Freemium model (API Key required).

Which MCP server has more tools and community activity?

Hipocampo lists 11 tools with 1 views and 3 GitHub stars. Moxie Docs MCP lists 12 tools with 17 views and 2 GitHub stars.

Can I use both Hipocampo and Moxie Docs MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

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

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

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

Hipocampo is listed under a Free / Open Source model with No auth required . Moxie Docs MCP operates under a Freemium model with API Key required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

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

Yes! MCP clients support multi-server orchestration. You can include both carrasquelalex1-hipocampo and moxie-docs-mcp as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Hipocampo has a Quality Score of 59 /100 ( Good ) with 1 views, 0 installs, and 3 GitHub stars. Moxie Docs MCP holds a Quality Score of 82 /100 ( Excellent ) with 17 views, 25 installs, and 2 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Hipocampo vs Moxie Docs MCP

In-depth architectural comparison of the Hipocampo and Moxie Docs MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Hipocampo

Knowledge & Memory · Remote HTTP/SSE

Quality: 59/100 (Good) | Auth: No auth required

Moxie Docs MCP

Knowledge & Memory · Local stdio

Quality: 82/100 (Excellent) | Auth: API Key required

Verdict Summary: Choose Hipocampo if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Moxie Docs MCP if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Hipocampo when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: memoria_vectorial, memory_items, related.

Explore Hipocampo Details

Choose Moxie Docs MCP when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: MOXIE_TOKEN.
Primary tools included: moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.

Explore Moxie Docs MCP Details

Feature & Specification Comparison

Specification	Hipocampo carrasquelalex1 Knowledge & Memory	Moxie Docs MCP FeaturedVerifiedKnowledge & Memory
Summary	Dual-memory MCP system (PostgreSQL 17 + pgvector + NVIDIA NIM). 11 tools: search, save, profile, health, auto-repair, stats, tune, dedup, checkpoint, maintenance. Sparse Selective Caching (SSC) with 4-phase progressive retrieval. Bilingual EN/ES. python scripts/hipocampomcpserver.py	MCP & Agent Skills for Automated Documentation, and codebase conventions + context
Category & Scope

Tools & Capabilities Breakdown

Hipocampo Tools (11)

memoria_vectorial

memory_items

follow_up

part_of

references

similar

chain

episodica

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Hipocampo Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "carrasquelalex1-hipocampo": {
      "url": "https://alexbell1-hipocampo-mcp.hf.space/mcp"
    }
  }
}

Moxie Docs MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "moxie-docs-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "moxie-docs"
      ],
      "env": {
        "MOXIE_TOKEN": "YOUR_MOXIE_TOKEN_HERE"
      }
    }
  }
}

Frequently Asked Questions

Hipocampo is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Moxie Docs MCP belongs to Knowledge & Memory using local stdio subprocess. Select Hipocampo when you need capabilities focused on knowledge & memory and Moxie Docs MCP when you require tools for knowledge & memory.

More alternatives to Hipocampo More alternatives to Moxie Docs MCP Knowledge & Memory category hub