What is the key difference between Genesys Memory and Corvid?

Genesys Memory belongs to the Knowledge & Memory category with local stdio execution, while Corvid belongs to the Knowledge & Memory category with cloud HTTP/SSE execution.

How do I install Genesys Memory or Corvid 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 Genesys Memory and Corvid free or paid?

Genesys Memory operates under a Free / Open Source model (No auth required). Corvid operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Genesys Memory lists 0 tools with 0 views and 0 GitHub stars. Corvid lists 0 tools with 0 views and 0 GitHub stars.

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

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

Yes! MCP clients support multi-server orchestration. You can include both genesys-memory and corvid 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, Genesys Memory has a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Corvid holds a Quality Score of 42 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Genesys Memory vs Corvid

In-depth architectural comparison of the Genesys Memory and Corvid 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

Genesys Memory

Knowledge & Memory · Local stdio

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

Corvid

Knowledge & Memory · Remote HTTP/SSE

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

Verdict Summary: Choose Genesys Memory if you need specialized Knowledge & Memory tools running via a local process. Choose Corvid if your workspace requires Knowledge & Memory integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Genesys 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 Genesys Memory Details

Choose Corvid 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 Corvid Details

Feature & Specification Comparison

Specification	G Genesys Memory Knowledge & Memory	C Corvid Knowledge & Memory
Summary	Open-source causal memory for AI agents: persistent, explainable, MCP-native memory (13 tools).	Free, no-signup persistent memory for AI agents: remember & recall across sessions.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

Genesys Memory Tools (0)

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

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

Genesys Memory Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "genesys-memory": {
      "command": "npx",
      "args": [
        "-y",
        "genesys-memory"
      ]
    }
  }
}

Corvid Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "corvid": {
      "url": "https://corvid.perch-app.workers.dev"
    }
  }
}

Frequently Asked Questions

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

More alternatives to Genesys Memory More alternatives to Corvid Knowledge & Memory category hub Canonical compare URL

Related MCP Server Comparisons

Popular comparisons with Genesys Memory

Popular comparisons with Corvid

Corvid vs Moxie Docs MCP