ThreadPage

page.threadPublished by thread.pageOfficial publisherv1.12.0Updated Nov 5, 2026

Read, search and add notes in your ThreadPage threads. On Free it adds notes to your Inbox.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

ThreadPage connects an AI session to your ThreadPage threads so it can read, search and add notes, and take requests you address to it.

What you can do
  • Read and search notes in your ThreadPage threads
  • Add notes to threads, or to your Inbox on Free or Pro without Sync
  • Take requests you address to the session's own name and act on them in that session
  • Connect a session under a name suggested from its folder, approved once in the browser
When to use it
Useful if you keep notes and threads in ThreadPage and want a Claude Code or Codex session to read them, add to them, or pick up requests you send from elsewhere in ThreadPage.
Requirements
A remote endpoint at thread.page with OAuth sign-in, approved once in the browser per connection. The Claude Code and Codex plugins need macOS, Linux or Windows via WSL, with Node.js 22.20+ on Node 22 or 24.8+. Native Windows is not supported. Reading threads and taking requests require a Pro plan with Sync on.
Before you install
Requests addressed to a session run with that session's own mode, rules and approvals, so a session that skips approval prompts carries them out without asking; set crossSessionInbound to hold or refuse to prevent self-starting requests. On Free or Pro without Sync it only writes to your Inbox. Your notes are read by the connected session when Sync is on.

Installation

In SourceWeft

  1. Open ThreadPage in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/page.thread%2Fthreadpage/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "threadpage": {
      "type": "http",
      "url": "https://thread.page/mcp"
    }
  }
}

README

ThreadPage local clients

The ThreadPage plugins for Claude Code and Codex: each session you connect gets its own name in ThreadPage. On ThreadPage Pro with Sync on, the session reads your threads, adds notes, and takes the requests you address to its @name. On Free, or on Pro without Sync, it only adds notes to your Inbox: it doesn't read your notes and takes no requests. A name whose access you never changed follows your plan: once you're on Pro with Sync on, it reads, adds and takes requests too. Only you, the account's owner, can address a request to your sessions.

This repository is a read-only mirror. It is updated only from tagged ThreadPage releases, and changes are made only by ThreadPage. To report a security problem, see SECURITY.md.

The plugins run on macOS, Linux and Windows through WSL, and need Node.js 22.20 or later on Node 22, or 24.8 or later. Native Windows isn't supported: the Claude Code plugin's hooks need sh, and there neither plugin keeps this computer's ThreadPage key between sessions.

Claude Code

sh
claude plugin install threadpage --marketplace ThreadPage/threadpage-companion

Then, in a Claude Code session, /threadpage:connect connects it under a name suggested from its folder (/threadpage:connect as <name> picks one); you approve it once in ThreadPage in your browser. A request addressed to the session reaches it through its inbox and doesn't wait for anyone at the terminal: an idle session starts a turn by itself, a busy one reads it between tool calls. It runs with that session's own mode, rules and approvals, so a session that skips approval prompts carries it out without asking. To keep requests from starting by themselves, set "Messages from your other sessions" (crossSessionInbound) in /config to hold or refuse; /threadpage:next then takes them.

Codex

sh
codex plugin marketplace add ThreadPage/threadpage-companioncodex plugin add threadpage@threadpage

Then start a new Codex session, send it any message, and type $threadpage:connect (or $threadpage:connect as <name>); you approve each connection in ThreadPage in your browser. A request addressed to the session starts once it has no running turn, with the session's own sandbox and approval settings, so under --ask-for-approval never it runs without asking; $threadpage:next takes the oldest waiting request. Live in ThreadPage means the Codex session is loaded, not that anyone is looking at it. To stop requests from starting in a session, Disconnect it in ThreadPage. To give a Codex session only its own name, start it with codex --disable apps, so the ChatGPT apps connector does not add a second ThreadPage connection.

More

What each plugin runs, sends and keeps: plugins/threadpage/README.md, plugins/threadpage-codex/README.md and SECURITY.md. RELEASES.json lists each release and the version of each client in it; CHANGELOG.md has each release's notes and, from the second release on, a link to its changes.

Source: README.md at commit 6b26845

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.12.0LatestNov 5, 2026

Score

85% 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
  • Auth declaredRequired10 pts
  • 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
  • License10 pts

Other Thread integrations

Mcp Reddit Search Thread Scraper

com.mambabuilt

Searches Reddit by keyword, subreddit or thread URL and returns flat rows of posts and comments, via an Apify actor.

STDIODesktop only
Web Search & Scraping1 toolNov 3, 2026

MindThread

Published by GitHub account ppcvote

MindThread lets an assistant write, schedule and publish Threads posts, review drafted replies and read account insights through Meta's official Threads API.

Streamable HTTPWeb executable
Productivity & Workflow40 toolsOct 26, 2026

Eclipse Thread MCP

Published by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLC

Local stdio MCP server offering on-prem bridges to a legacy software-engineering toolchain, plus an "Evidence Weaver" that joins results.

STDIODesktop only
Developer ToolsNot validated yetOct 27, 2026

Kairos Coordination Thread

Published by GitHub account agentindexworld

Free MCP tools to validate multi-agent coordination thread turns and retrieve schema/samples.

Streamable HTTPWeb executable
Not indexed yetOct 25, 2026

EchoThread

io.echothread

Lets an assistant read and moderate EchoThread site comments — pending queue, approve, reject, spam, reply and delete — without opening the dashboard.

STDIODesktop only
Communication & CollaborationNot validated yetNov 5, 2026