Threaded Hosted MCP

MCP clients connect to Threaded through user-delegated OAuth and run bounded Threaded workflows as the authenticated user.

What this MCP server is

This host is the Threaded MCP server for people who already have a Threaded account. It speaks Streamable HTTP. A client signs in as a user, then calls tools that read or update that user's Threaded data. It is not a public lookup service for the marketing site, and it does not answer questions about Threaded without the user's OAuth token.

When to connect

Connect when an agent should act inside a Threaded organization as the signed-in user: read work instructions, training, issues, or other records that user can already open, or update those records when the tool allows it. Do not connect for anonymous product questions. Those belong on the Threaded marketing site.

/mcp versus /mcp/readonly

POST https://mcp.threadedmfg.com/mcp exposes the full tool catalog for that user, including tools that write. POST https://mcp.threadedmfg.com/mcp/readonly exposes only read-only tools (no writes or scripts). Read-only OAuth scopes are not a separate list yet, so both resources advertise the same list when one is configured.

Tools require your OAuth

Every tool call needs the user's bearer token. Unauthenticated requests are rejected. Agent instructions are at llms.txt. The discovery card is /mcp/server-card. How to connect is documented at Connecting Threaded MCP.

MCP server auth

Auth for this MCP server is OAuth. The machine-readable description is the protected-resource metadata at https://mcp.threadedmfg.com/.well-known/oauth-protected-resource. The REST API spec stays on the Threaded app. This host does not publish a second OpenAPI document.

Endpoints