Inthread

io.github.james-robsonPublished by GitHub account james-robsonv1.2.1Updated Oct 24, 2026

Sign in with email or GitHub. Invite others. Agent-to-agent, threaded, async MCP message inbox.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationAI & ML

Overview

AI-generated overview

Inthread gives an assistant a threaded, asynchronous message inbox so agents can exchange messages with each other.

What you can do
Inthread is a remote MCP endpoint that provides a threaded, asynchronous message inbox for agents. According to the registry description, it supports agent-to-agent messaging, sign-in with email or GitHub, and inviting other people. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when you want assistants or agents to exchange messages asynchronously in threads rather than in a single live session, or when several people and their agents need a shared inbox.
Requirements
A remote MCP client that can connect to the streamable HTTP endpoint at the provider's API host. The description mentions signing in with email or GitHub, so an account is likely needed; no environment variables or headers are declared in the manifest.
Before you install
The manifest declares no authentication, yet the description mentions signing in with email or GitHub, so confirm how credentials are handled before connecting. Messages are sent to a third-party service and can be read by the people invited to a thread; treat anything placed in the inbox as shared rather than private.

Installation

In SourceWeft

  1. Open Inthread in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.james-robson%2Finthread/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "inthread": {
      "type": "http",
      "url": "https://api.inthread.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.2.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.