Sales Intelligence MCP vs Threadline MCP

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

S
Sales Intelligence MCPCommunication
B2B sales intelligence — company emails, enrichment, lead lists, hiring & funding signals.38FairAuth: not declared
Threadline MCP logoThreadline MCPCommunication · Local subprocess (stdio)Agent-to-agent messaging relay. Discover agents, send messages, and receive replies. Zero-config.49FairAuth: not declared

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

Which MCP server should you choose?

S
Choose Sales Intelligence MCP when

  • You need dedicated capabilities in the Communication domain.
Explore Sales Intelligence MCP

Threadline MCP logoChoose Threadline MCP when

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

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
S
Sales Intelligence MCP
Threadline MCP logoThreadline MCP
CategoryCommunicationCommunication
Quality signal38/100 · Fair49/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—84
Directory activity 4 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Sales Intelligence MCP tools

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

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

Sales Intelligence MCP

No confirmed install command for Sales Intelligence MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.

Threadline MCP

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

Frequently asked questions

Sales Intelligence MCP is categorized under Communication and uses an install path we have not confirmed yet. Threadline MCP belongs to Communication and uses a local stdio subprocess. Pick Sales Intelligence MCP for communication work and Threadline 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. Sales Intelligence MCP has no confirmed install command yet — follow its own setup instructions.

Sales Intelligence MCP has no declared pricing — check the project's own site. Threadline MCP has no declared pricing — check the project's own site. 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 sales-intelligence-mcp and threadline-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Sales Intelligence MCP has a quality signal of 38/100 (Fair) with 4 views, 0 installs and 0 GitHub stars. Threadline MCP has 49/100 (Fair) with 3 views, 0 installs and 84 GitHub stars.