A side-by-side look at the Covalent Bond and Threadline MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Covalent Bond for communication work as a local process; choose Threadline MCP for communication as a local process. You can also run both side by side in one mcpServers block.
COVALENT_RELAY_URL, COVALENT_MAX_FILE_KB.bond_connect, bond_join, bond_send.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 61/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | Not declared |
| Pricing | Free | Not declared |
| Required env vars | COVALENT_RELAY_URLCOVALENT_MAX_FILE_KB | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 81 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 9 | Not listed |
| Full listing | View Covalent Bond | View Threadline MCP |
bond_connectCreate a new Covalent Bond session and get a shareable session code. The other agent will use this code to join.bond_joinJoin an existing Covalent Bond session using a session code (format: XXXX-XXXX-XXXX Base58, e.g., "3KPz-QR7m-8WXn"). Call this when the user provides a session code from another agent. The code is a shared secret - it authenticates the encrypted channel and is never sent to the relay.bond_sendSend a file to the connected agent. File will be encrypted and delivered with an optional message. Subject to 10-second rate limit and security validation (file type whitelist, 256KB default size limit, configurable via COVALENT_MAX_FILE_KB).bond_acceptAccept a pending file transfer. File will be written to ~/.covalent/incoming/ and its content returned, wrapped in untrusted-data markers.bond_declineDecline a pending file transfer. File will be discarded and sender will not be notified.bond_messageSend a short encrypted text message to the connected agent (no file involved). Use this for agent-to-agent conversation: questions, context, summaries. Requires a confirmed session. Max 4000 characters.bond_waitWait (long-poll) until the next event arrives from the peer (a message, incoming file, or disconnect) or until the timeout passes. Use this in a loop to hold a live conversation with the other agent: call bond_wait, react to what it returns, reply, call bond_wait again. Returns immediately if events are already queued. This costs tokens per call, so loop only during an active conversation; for idle waiting rely on desktop notifications and bond_status.bond_statusGet current Covalent Bond connection status: session info, handshake state, pending file transfers, and any events (incoming transfers, peer messages) that arrived since the last tool call. Call this periodically while connected to pick up incoming transfers.bond_endEnd the current Covalent Bond session and disconnect from relay. Clears all pending transfers.No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"gopalrajsuresh-covalent-bond": {
"command": "npx",
"args": [
"-y",
"covalent-bond"
],
"env": {
"COVALENT_RELAY_URL": "YOUR_COVALENT_RELAY_URL_HERE",
"COVALENT_MAX_FILE_KB": "YOUR_COVALENT_MAX_FILE_KB_HERE"
}
}
}
}
{
"mcpServers": {
"threadline-mcp": {
"command": "npx",
"args": [
"-y",
"instar"
]
}
}
}
