COTI Private Messaging vs Courier

In-depth architectural comparison of the COTI Private Messaging and Courier 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 COTI Private Messaging when:

• You need dedicated capabilities in the Communication domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore COTI Private Messaging Details

Choose Courier when:

• You need dedicated capabilities in the Communication domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Courier Details

Feature & Specification Comparison

Specification	COTI Private Messaging Communication	Courier Communication
Summary	Private encrypted agent messaging, hidden state exchange, delegation, and private inbox workflows.	Continuity protocol for autonomous AI agents. Agent messaging with SMTP bridge and LN payments.
Category & Scope	Communication	Communication

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": {
    "coti-private-messaging": {
      "command": "npx",
      "args": [
        "-y",
        "-p"
      ]
    }
  }
}

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

Related MCP Server Comparisons