Log inSubmit server

Agent Comms vs Sales Intelligence MCP

A side-by-side look at the Agent Comms and Sales Intelligence MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Agent Comms logoAgent CommsCommunication · Local subprocess (stdio)Cross-harness communication mesh for LLM agents — rooms, DMs, presence, and visibility over TCP49FairAuth: not declared
S
Sales Intelligence MCPCommunication · Remote HTTP/SSEB2B sales intelligence — company emails, enrichment, lead lists, hiring & funding signals.40FairAuth: api key required

Verdict: choose Agent Comms for communication work as a local process; choose Sales Intelligence MCP for communication over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Agent Comms logoChoose Agent Comms when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
Explore Agent Comms

S
Choose Sales Intelligence MCP when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: API key required.
Explore Sales Intelligence MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAgent Comms logoAgent Comms
S
Sales Intelligence MCP
CategoryCommunicationCommunication
Quality signal49/100 · Fair40/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredAPI key required
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars34—
Directory activity 1 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView Agent Comms View Sales Intelligence MCP

Tools & capabilities

Agent Comms tools

No tool names declared yet. Check the project README from the listing page.

Sales Intelligence MCP tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Agent Comms

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "agent-comms": {
      "command": "npx",
      "args": [
        "-y",
        "agent-comms"
      ]
    }
  }
}

Sales Intelligence MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "sales-intelligence-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "sales-intelligence-mcp"
      ]
    }
  }
}

Frequently asked questions

Agent Comms is categorized under Communication and uses a local stdio subprocess. Sales Intelligence MCP belongs to Communication and uses a remote HTTP/SSE transport. Pick Agent Comms for communication work and Sales Intelligence MCP for communication.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Agent Comms has no declared pricing — check the project's own site. Sales Intelligence MCP has no declared pricing — check the project's own site. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add agent-comms and sales-intelligence-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Agent Comms has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 34 GitHub stars. Sales Intelligence MCP has 40/100 (Fair) with 4 views, 0 installs and 0 GitHub stars.

Popular comparisons with Agent Comms

Popular comparisons with Sales Intelligence MCP