What is the key difference between Mcp and EvolutionDB Long Term Memory?

Mcp belongs to the Knowledge & Memory category with cloud HTTP/SSE execution, while EvolutionDB Long Term Memory belongs to the Knowledge & Memory category with local stdio execution.

How do I install Mcp or EvolutionDB Long Term Memory 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 Mcp and EvolutionDB Long Term Memory free or paid?

Mcp operates under a Free / Open Source model (No auth required). EvolutionDB Long Term Memory operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Mcp lists 0 tools with 0 views and 0 GitHub stars. EvolutionDB Long Term Memory lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Mcp and EvolutionDB Long Term Memory 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 Mcp or EvolutionDB Long Term Memory 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 Mcp and EvolutionDB Long Term Memory free to use, or do they require API keys?

Mcp is listed under a Free / Open Source model with No auth required . EvolutionDB Long Term Memory operates under a Free / Open Source model with No auth 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 Mcp and EvolutionDB Long Term Memory at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both mcp-160 and evolutiondb-long-term-memory 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, Mcp has a Quality Score of 42 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars. EvolutionDB Long Term Memory holds a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Mcp vs EvolutionDB Long Term Memory

In-depth architectural comparison of the Mcp and EvolutionDB Long Term Memory 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

Mcp

Knowledge & Memory · Remote HTTP/SSE

Quality: 42/100 (Fair) | Auth: No auth required

EvolutionDB Long Term Memory

Knowledge & Memory · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Mcp if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose EvolutionDB Long Term Memory 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 Mcp 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).

Explore Mcp Details

Choose EvolutionDB Long Term Memory when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore EvolutionDB Long Term Memory Details

Feature & Specification Comparison

Specification	M Mcp Knowledge & Memory	E EvolutionDB Long Term Memory Knowledge & Memory
Summary	Wontopos (WOS) long-term memory — one memory across Claude Code, Cursor, ChatGPT, and your agents.	Persistent long-term memory for Claude Desktop / Claude Code, backed by EvolutionDB.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

Mcp Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

EvolutionDB Long Term Memory Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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

Mcp Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mcp-160": {
      "url": "https://wontopos.com"
    }
  }
}

EvolutionDB Long Term Memory Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "evolutiondb-long-term-memory": {
      "command": "npx",
      "args": [
        "-y",
        "evolutiondb-long-term-memory"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Mcp More alternatives to EvolutionDB Long Term Memory Knowledge & Memory category hub Canonical compare URL

Related MCP Server Comparisons

Popular comparisons with Mcp

Popular comparisons with EvolutionDB Long Term Memory

EvolutionDB Long Term Memory vs Moxie Docs MCP