ThreadPage MCP server
Commit Nov 10, 2026Connects AI coding agents like Claude Code and Codex to your ThreadPage threads to read, search, and add notes.
Also known as ThreadPage/threadpage-companion, threadpage-companion
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.12.0
- Last commit
- Nov 10, 2026
- License
- Apache-2.0
What is ThreadPage MCP?
ThreadPage connects AI coding agents like Claude Code and Codex to your ThreadPage threads to read, search, and add notes.
Summary generated from the project's README
About ThreadPage MCP server
ThreadPage provides a way for AI coding agents to interact with your project notes. Developers using Claude Code or Codex can connect their sessions to ThreadPage threads to read existing information, search through notes, and add new entries. This connection allows an agent to act as a participant in your documentation process, using its own rules and approval settings to manage tasks.
Setup varies depending on your subscription and environment. On ThreadPage Pro with Sync enabled, sessions can read threads and respond to requests via an @name. Free users can only add notes to an Inbox. The plugins run on macOS, Linux, or Windows via WSL and require Node.js 22.20 or later. For a standard MCP connection, users can connect Claude, ChatGPT, or Codex through the ThreadPage MCP server using OAuth sign-in in a browser.
Beyond simple note-taking, the Handoff skill allows agents to record their status, such as being blocked or finished, into a local directory. This ensures that subsequent sessions can pick up exactly where the previous one left off by reading the last recorded state.
What you can do with it
- 1Sync project notes with agentsConnect a Claude Code session to your project threads so the agent can read and add notes automatically.
- 2Manage session handoffsUse the Handoff skill to write the current session status to a local file for the next agent to read.
- 3Remote agent communicationSend requests to an idle Claude Code or Codex session from another thread to trigger a task.
- 4Centralized note organizationDirect all agent-generated notes to a single inbox if you are using the free version of the service.
Written from the project's README. Every use case is checked against a quote from it.
How to install ThreadPage MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall ThreadPage MCP in Claude Code
$ claude mcp add --transport http threadpage-companion https://thread.page/mcpInstall ThreadPage MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"threadpage-companion": {
"url": "https://thread.page/mcp"
}
}
}Install ThreadPage MCP in VS Code
.vscode/mcp.json
{
"servers": {
"threadpage-companion": {
"type": "http",
"url": "https://thread.page/mcp"
}
}
}Install ThreadPage MCP in VS Code CLI
$ code --add-mcp '{"name":"threadpage-companion","type":"http","url":"https://thread.page/mcp"}'Install ThreadPage MCP in Codex
$ codex mcp add threadpage-companion --url https://thread.page/mcpInstall ThreadPage MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.threadpage-companion] url = "https://thread.page/mcp"
Install ThreadPage MCP in Gemini CLI
$ gemini mcp add -s user --transport http threadpage-companion https://thread.page/mcpInstall ThreadPage MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"threadpage-companion": {
"url": "https://thread.page/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablethreadpage/threadpage-companion is public and reachablegithub.com/threadpage/threadpage-companion ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-10github.com/threadpage/threadpage-companion ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubThreadPage plugins for Claude Code and Codex
ThreadPage keeps each project in one thread of notes. These plugins connect your Claude Code and Codex sessions to it, each under its own @name. On ThreadPage Pro with Sync on, a session reads your threads and adds notes, and you ask it from any thread by its @name; on Free, it adds notes to your Inbox (Free and Pro). Step by step: thread.page/help/connections/coding-agents.
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
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
codex plugin marketplace add ThreadPage/threadpage-companion
codex 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, set Who can ask it to No one, or Pause 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.
Free and Pro
On ThreadPage Pro with Sync on, a connected session reads your threads and adds notes, and you ask it by its @name. On Free, or on Pro without Sync, it only adds notes to your Inbox: it doesn't read your notes and no one can ask it. A name whose access you never changed follows your plan: once you're on Pro with Sync on, it reads, adds and can be asked too. Only you can send a request, unless you let your agents ask each other. Anything else waits for your permission. You can try Pro free for 14 days, once per email address, without a card: thread.page/pricing.
Handoff
A free skill for Claude Code, Codex and any agent that reads skills: it writes where a session stopped (done, left, blocked) into .handoff/ in your project, and reads the last handoff back in the next session. It needs no account and runs no hooks or server. With ThreadPage's tools in the session, a copy goes to your Inbox, or on Pro with Sync on to a thread the next session reads.
claude plugin install handoff --marketplace ThreadPage/threadpage-companion
codex plugin marketplace add ThreadPage/threadpage-companion
codex plugin add handoff@threadpage
npx skills add ThreadPage/threadpage-companion --skill handoff
How to use it and how to keep it in a repository: plugins/handoff/README.md. With the plugins above on Pro with Sync on, connecting a session in that folder also shows it the last handoff of the thread in .handoff/thread, and asks it to add a note there.
The MCP server
Claude, ChatGPT, Claude Code and Codex can also connect to your notes through the ThreadPage MCP server at https://thread.page/mcp, with OAuth sign-in in your browser: thread.page/help/connections/mcp. In a Claude Code session you connect with the plugin, don't also add the server with claude mcp add: what the session does through it is then added via Claude Code, not under the session's own name.
More
What each plugin runs, sends and keeps: plugins/threadpage/README.md, plugins/threadpage-codex/README.md, plugins/handoff/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.
- ThreadPage: thread.page
- What each connection can do, and how to undo what it did: thread.page/help/connections
- Privacy: thread.page/privacy
ThreadPage MCP questions
How do I add ThreadPage MCP to Claude Code?
Run claude mcp add --transport http threadpage-companion https://thread.page/mcp in your terminal. Add --scope user to make it available in every project.
How do I add ThreadPage MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What is the difference between Free and Pro plans for the plugins?
On ThreadPage Pro with Sync on, sessions can read threads and be addressed by @name. On Free, sessions only add notes to your Inbox and cannot read your notes.
Does the plugin work on Windows?
The plugins run on macOS, Linux, and Windows via WSL, but native Windows is not supported because the Claude Code plugin requires sh.