Directory vs WingmanProtocol Agent Gateway

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

Which MCP Server Should You Choose?

Choose Directory 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).
• Primary tools included: Four independent memory layers so one layer's failure doesn't cascade, Local-LLM memory service (Qwen 3.5 9B via Ollama) for truth extraction and indexing, Qdrant vector database plus Mem0 for semantic memory.

Explore Directory Details

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 (Freemium).
• Primary tools included: Durable agent registration, memory, and resume lifecycle, Persistent real headless browser with cookies and login sessions, Background errands, artifacts, and cited deep-research reports.

Feature & Specification Comparison

Specification	Directory Knowledge & Memory	WingmanProtocol Agent Gateway Knowledge & Memory
Summary
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

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

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

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

Related MCP Server Comparisons