What is the key difference between Corvid and Recall?

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

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

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

Which MCP server has more tools and community activity?

Corvid lists 0 tools with 0 views and 0 GitHub stars. Recall lists 0 tools with 0 views and 0 GitHub stars.

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

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

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

Side-by-Side Model Context Protocol Comparison

Corvid vs Recall

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

Corvid

Knowledge & Memory · Remote HTTP/SSE

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

Recall

Knowledge & Memory · Local stdio

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

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

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

Feature & Specification Comparison

Specification	C Corvid Knowledge & Memory	R Recall Knowledge & Memory
Summary	Free, no-signup persistent memory for AI agents: remember & recall across sessions.	Open-source MCP memory server. Persistent, searchable, tiered memory across sessions.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

Corvid Tools (0)

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

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

Corvid Configuration

mcpServers (Claude Desktop / Cursor)

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

Recall Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "recall-2": {
      "command": "npx",
      "args": [
        "-y",
        "recall-2"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Corvid More alternatives to Recall Knowledge & Memory category hub

Related MCP Server Comparisons

Popular comparisons with Corvid

Popular comparisons with Recall

Recall vs Moxie Docs MCP