Threadline MCP logo

Threadline MCP

Agent-to-agent MCP relay for discovering agents, sending messages, and receiving replies with zero configuration.

Install Threadline MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "threadline-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "instar"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

threadline-mcp provides an agent-to-agent messaging relay through MCP tools. Agents can discover other agents, send messages, and receive replies without configuring a separate messaging workflow. Reach for it when an agent needs to locate another agent and exchange information or requests. The relay is described as zero-config.

Use cases

  • Discover agents that can handle a delegated task
  • Send requests between specialized agents
  • Receive replies from peer agents
  • Coordinate multi-agent workflows

Key features

  • Agent discovery
  • Agent-to-agent message relay
  • Reply handling
  • Zero-configuration operation

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

25/26 checks healthy over the last 92d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · instar (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars86Stargazers on the source repository.
npm downloads180kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Threadline MCP works

What threadline-mcp does

threadline-mcp provides an MCP interface for communication between agents. Its core function is relaying messages from one agent to another and returning replies to the requesting workflow.

The server is intended for multi-agent systems in which agents need to find one another before communicating. Discovery, outbound messaging, and reply handling are the central capabilities. This makes it suitable for delegating a request, consulting another specialized agent, or coordinating work across multiple agent instances.

The relay focuses on agent-to-agent communication rather than human-facing channels. A consuming agent uses MCP to access the relay's capabilities from its host environment.

How it works

An agent starts by discovering available agents through the relay. After identifying a destination, it can send a message to that agent and wait for or retrieve the resulting reply. The returned response can then be used in the originating agent's task or passed into a larger multi-agent workflow.

This interaction model separates agent discovery from message exchange. An agent does not need to know every peer in advance; it can use discovery to identify a communication target, then use the messaging flow to contact it.

The server is described as zero-config, so the intended setup does not require a collection of relay-specific settings before agents can communicate. The exact hosting and transport arrangement depends on the MCP client and runtime used to launch it.

Setup and configuration

threadline-mcp is presented as a zero-configuration agent messaging relay. Configure it through the MCP-compatible host that will run the server, then make its capabilities available to the agent that needs to communicate with peers.

No environment variables or relay-specific configuration values are required by the available description. The important deployment concern is ensuring that the participating agents are reachable through the same relay context and can be identified during discovery.

Tools and capabilities

  • Discover agents available through the relay.
  • Send messages from one agent to another.
  • Receive replies from contacted agents.
  • Support multi-agent workflows that require peer discovery and communication.

These capabilities can be combined into a simple delegation sequence: find a suitable agent, send it a request, and use its reply in the originating task.

Limitations and notes

threadline-mcp is focused on agent-to-agent messaging. It should be evaluated as a communication relay rather than as a general-purpose task system, memory store, or human messaging integration.

The available capabilities are described at a high level as discovery, message sending, and reply receipt. Teams choosing it should confirm that its communication model matches their required delivery, routing, authentication, and persistence behavior before depending on it for production coordination.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Threadline MCP

threadline-mcp is an MCP server that connects agents through an agent-to-agent messaging relay and provides tools to discover agents, send messages, and receive replies. It is intended for workflows where one agent needs to locate another, exchange a request or message, and handle the resulting response without a separate messaging setup.

Use threadline-mcp through an MCP-compatible host with its zero-configuration relay model. The available setup information does not require relay-specific environment variables or configuration values; the host must make the server available to the agent.

Agents can discover peers, send messages, and receive replies. These operations support delegation and coordination workflows in which one agent locates another agent, requests work or information, and incorporates the response.

Yes, threadline-mcp is designed for multi-agent communication. Its discovery and messaging capabilities let an agent identify another agent, send it a message, and receive the resulting reply.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewThreadline MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/threadline-mcp?style=directory)](https://allmcps.com/mcp/threadline-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/threadline-mcp"><img src="https://allmcps.com/api/badge/threadline-mcp?style=directory" alt="Threadline MCP on AllMCPs" /></a>