WingmanProtocol Agent Gateway vs IWE

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

W

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 IWE 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 IWE Details

Feature & Specification Comparison

Specification	W WingmanProtocol Agent Gateway Knowledge & Memory	IWE Knowledge & Memory
Summary	Register once, resume your whole self in one call. Real browser, deep research, durable memory.	Markdown knowledge base as agent memory. Runs against the notes directory it is started in.
Category & Scope	Knowledge & Memory	Knowledge & Memory

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": {
    "wingmanprotocol-agent-gateway": {
      "command": "npx",
      "args": [
        "-y",
        "wingmanprotocol-agent-gateway"
      ]
    }
  }
}

{
  "mcpServers": {
    "iwe": {
      "command": "npx",
      "args": [
        "-y",
        "@iwe-org/mcp"
      ]
    }
  }
}

Related MCP Server Comparisons