What is the key difference between WingmanProtocol Agent Gateway and Agent Recall?

WingmanProtocol Agent Gateway belongs to the Knowledge & Memory category with local stdio execution, while Agent Recall belongs to the Knowledge & Memory category with local stdio execution.

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

WingmanProtocol Agent Gateway operates under a Free / Open Source model (No auth required). Agent Recall operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

WingmanProtocol Agent Gateway lists 0 tools with 0 views and 0 GitHub stars. Agent Recall lists 0 tools with 1 views and 365 GitHub stars.

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

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

Yes! MCP clients support multi-server orchestration. You can include both wingmanprotocol-agent-gateway-2 and agent-recall 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, WingmanProtocol Agent Gateway has a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Agent Recall holds a Quality Score of 47 /100 ( Fair ) with 1 views, 0 installs, and 365 GitHub stars.

Side-by-Side Model Context Protocol Comparison

WingmanProtocol Agent Gateway vs Agent Recall

In-depth architectural comparison of the WingmanProtocol Agent Gateway and Agent 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

WingmanProtocol Agent Gateway

Knowledge & Memory · Local stdio

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

Agent Recall

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose WingmanProtocol Agent Gateway if you need specialized Knowledge & Memory tools running via a local process. Choose Agent 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 WingmanProtocol Agent Gateway 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 WingmanProtocol Agent Gateway Details

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

Feature & Specification Comparison

Specification	W WingmanProtocol Agent Gateway Knowledge & Memory	A Agent Recall Knowledge & Memory
Summary	Durable self for AI agents: one-call resume, memory, real browser, free chat + hire real humans.	Correction-first agent memory. Precision KPI tracks if agents heed warnings. 5 layers, local-only.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

WingmanProtocol Agent Gateway Tools (0)

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

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

WingmanProtocol Agent Gateway Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "wingmanprotocol-agent-gateway-2": {
      "command": "npx",
      "args": [
        "-y",
        "wingmanprotocol-agent-gateway-2"
      ]
    }
  }
}

Agent Recall Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

WingmanProtocol Agent Gateway is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Agent Recall belongs to Knowledge & Memory using local stdio subprocess. Select WingmanProtocol Agent Gateway when you need capabilities focused on knowledge & memory and Agent Recall when you require tools for knowledge & memory.

More alternatives to WingmanProtocol Agent Gateway More alternatives to Agent Recall Knowledge & Memory category hub Canonical compare URL