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

EvolutionDB Long Term Memory belongs to the Knowledge & Memory category with local stdio execution, while Github Twin belongs to the Knowledge & Memory category with local stdio execution.

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

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

Which MCP server has more tools and community activity?

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

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

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

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

Side-by-Side Model Context Protocol Comparison

EvolutionDB Long Term Memory vs Github Twin

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

EvolutionDB Long Term Memory

Knowledge & Memory · Local stdio

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

Github Twin

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose EvolutionDB Long Term Memory if you need specialized Knowledge & Memory tools running via a local process. Choose Github Twin 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 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

Choose Github Twin 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 Github Twin Details

Feature & Specification Comparison

Specification	E EvolutionDB Long Term Memory Knowledge & Memory	G Github Twin Knowledge & Memory
Summary	Persistent long-term memory for Claude Desktop / Claude Code, backed by EvolutionDB.	Personal RAG over your GitHub history (commits, code, reviews), served to Claude Code over MCP.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

EvolutionDB Long Term Memory Tools (0)

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

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

EvolutionDB Long Term Memory Configuration

mcpServers (Claude Desktop / Cursor)

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

Github Twin Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "github-twin": {
      "command": "uvx",
      "args": [
        "github-twin"
      ]
    }
  }
}

Frequently Asked Questions

EvolutionDB Long Term Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Github Twin belongs to Knowledge & Memory using local stdio subprocess. Select EvolutionDB Long Term Memory when you need capabilities focused on knowledge & memory and Github Twin when you require tools for knowledge & memory.

More alternatives to EvolutionDB Long Term Memory More alternatives to Github Twin Knowledge & Memory category hub