Connections
Let an assistant work with selected published content in your cloud notebook. Your drafts stay private.
Client setup
Use the MCP URL from Settings → Connections in place of MCP_URL below.
Codex
codex mcp add threadpage --url MCP_URL --oauth-client-registration cimd
codex mcp login threadpage --scopes notebook.read,notebook.propose,notebook.add,notebook.editThe browser opens ThreadPage to let you choose access. Requesting a scope does not grant it: you can authorize read access alone. See the Codex authentication guide.
Claude Code
claude mcp add --transport http threadpage MCP_URL
claude mcp login threadpageFollow the browser sign-in and select your Threads. See the Claude Code MCP guide.
ChatGPT and other assistants
Add the MCP URL as a remote connection in your client. Connection availability depends on the client and account. ChatGPT client metadata is supported; its hosted connection has not yet been verified. Other clients need OAuth with PKCE and a registered client identity. Contact support if your client reports that its identity is unsupported.
Connect an assistant
Open Settings → Connections and copy the MCP URL. Add it as a remote MCP connection in your assistant, then sign in to ThreadPage. The authorization page lets you select exact Threads. Read access includes their current and future published Entries.
The client must support remote HTTP MCP and OAuth. Protocol support alone does not confirm compatibility with a particular assistant. Follow your client’s current connection instructions.
Choose how it can write
Prepare review links lets an assistant prepare content for selected destinations. Open its private link to inspect the content and destination, then choose Apply or Reject. Closing the page does neither. Applying requires active Pro cloud access.
Allow maintenance permits future writes to the exact selected targets without another Apply. The external client runs the work; ThreadPage enforces your minimum interval per target and action. Purpose and expected output describe your request, but do not constrain the meaning of generated text. Editing an Entry yourself does not stop maintenance.
If you allow creating Threads in a Folder or Unfiled, each created Thread becomes a read and append target for that permission. Other Threads are never included automatically. Remove any exact target in Manage access, stop maintenance, or revoke the connection.
Read what changed
Changes in notebook navigation shows additions and edits across your notebook. Filter by Thread and date, then inspect the exact retained before and after versions. Editing an old Entry does not move it in the notebook. Entry actions → Version history compares an earlier version with current accepted content.
The current version stays available. Replaced versions and original images remain for 90 days after replacement; dates and gaps are shown where available. New unapplied external edits are kept for 30 days. Retained history can still be read on Free.
Images and references
Review links can use existing readable images. Uploading new images requires an active maintenance write grant. Historical references link to the current original explicitly; previews never silently replace historical text.
Labels and recovery
“Added via” and “Edited via” describe the connection used, not a verified model or author. If a remote write conflicts, review its unapplied copy in Connections. Keep as new preserves its external origin; downloading a copy includes retained original images.
If a response is lost, retry the saved action. ThreadPage keeps its identity so a retry does not create another copy. Revocation ends remote access and invalidates unapplied review links.