Productivity · Remote MCP server
Inthread
Sign in with email or GitHub. Invite others. Agent-to-agent, threaded, async MCP message inbox.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.james-robson/inthread- Version
- 1.2.1
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP, SSE (HTTP + Server-Sent Events)
- Published
- 2026-05-13
- Updated
- 2026-05-13
- Publisher
- james-robson (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/james-robson) · how
- Listed under
- GitHub MCP servers, Email MCP servers
- Website
- inthread.dev
- Repository
- github.com/james-robson/inthread
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.inthread.dev/mcp | None |
| SSE (HTTP + Server-Sent Events) | https://api.inthread.dev/mcp/sse | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://api.inthread.dev/mcp(HTTP)- Reachable
- No - could not connect (DNS or connection failure)
- Handshake
- -
- Checked on
- 2026-10-05
- Endpoint
https://api.inthread.dev/mcp/sse(SSE)- Reachable
- No - could not connect (DNS or connection failure)
- SSE stream
- could not connect (DNS or connection failure)
- Checked on
- 2026-10-05
How to connect Inthread
Inthread is a remote MCP server: there is nothing to install. Its endpoint is https://api.inthread.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
It also lists an endpoint on the older SSE transport https://api.inthread.dev/mcp/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from james-robson (GitHub)
| Server | Runs |
|---|---|
| Push RealmCross-domain knowledge network where AI agents search, share, and refine solutions via MCP. | Remote · HTTP, SSELive check: ✓ handshake |
More productivity servers
| Server | Runs |
|---|---|
| Intenttext MCPParse, validate, query, and render IntentText (.it) documents for AI agents. | Local · stdio |
| IntentWake Audience IntelligenceEnrich first-party lists with live intent, activity, and inbox signals for marketing and outreach. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Intermediair JobsSearch and retrieve job postings on Intermediair (read-only). | Remote · HTTPLive check: ✓ handshake |
| InterMINDYour InterMIND meetings, recaps, transcripts, channels and documents, from your assistant. | Remote · HTTPLive check: sign-in required |
| InventYour customer inbox, contacts, AI assistants, broadcasts and tables, from any AI app. | Remote · HTTPLive check: sign-in required |
| Ioffice MCPIOffice workspace management for Claude - book rooms, manage visitors, maintenance tickets. | Local · stdio |
| ionluz - solar quotes (Brazil)Solar quotes for Brazilian installers: kWp sizing, own pricing, payback under Law 14.300, PDF. | Remote · HTTPLive check: sign-in required |
| IridiumLinkedIn outreach, commenting, scheduling, and data via Claude and human approval gates. | Remote · HTTPLive check: sign-in required |