Choose your assistant. Each card says how it connects, what has been verified with Readyweek, and what to do next. Writing guidance is included through the connection, so there is nothing to install.
Two ways to connect: browser sign-in for Claude Desktop and the ChatGPT desktop app, or a private key pasted once for Codex CLI, Claude Code, Gemini CLI and other MCP clients. Every path starts from your workspace after sign-in.
Custom connector · browser sign-in
Add Readyweek as a custom connector, sign in, and approve the workspace and Threads account. The Readyweek owner has reported drafting, review and publishing a post with an image through Claude, without recording which Claude surface was used. That is a reported result, not an independent test of this environment.
Desktop app · MCP server · browser sign-in
Add Readyweek under Settings, MCP servers, then authenticate in your browser. The path follows OpenAI’s documentation; a full sign-in, draft and approval run with Readyweek has not been recorded. ChatGPT web is not available.
Terminal · private key
Paste one setup request from your workspace into Codex; it stores a revocable key outside your repository. A local synthetic account-read check with Codex CLI passed against a loopback Readyweek server. Production onboarding, drafting and image upload through Codex have not been verified.
Terminal · private key
Paste one setup request from your workspace into Claude Code. A recorded synthetic-account read check exists from an earlier adapter build. Production onboarding, drafting and image upload through Claude Code have not been verified.
Terminal · private key
One setup request adds Readyweek to Gemini CLI with a private key. No check with Readyweek has been recorded for this client yet.
Streamable HTTP · bearer key · manual
Any client that supports Streamable HTTP with a bearer key can be configured by hand from the address and one-time key your workspace shows. Protocol support does not prove the client works end to end.
Sign in and create your workspace, then connect your Threads account through Meta.
Open Your assistant in the workspace and choose your client. Browser sign-in clients get the server address to paste; terminal clients get a one-time setup request to paste.
Ask the assistant to check its permissions, then ask for a draft and review it in Readyweek.
Already have a workspace? Sign in, choose the workspace, then open Your assistant.
| Assistant | Account reads | Drafts and review | Image transfer | Status |
|---|---|---|---|---|
| Claude Desktop (custom connector) | Not recorded for this client | Owner-reported through Claude; surface not recorded | Not recorded; the reported image post used an image already in Readyweek, which does not show agent upload | Not yet verified |
| ChatGPT desktop app | Not recorded | Not recorded | Not recorded | Not yet verified; docs checked 2026-08-31 |
| Codex CLI | Local synthetic read with Codex CLI 0.153.4 against a loopback server, 2026-09-06 | Not recorded | Not recorded; needs a file or terminal bridge | Local read verified |
| Claude Code | Synthetic-account read, milestone 3 validation, 2026-08-29 | Not recorded | Not recorded | Local read verified |
| Gemini CLI | Not recorded | Not recorded | Not recorded | Not yet verified |
| ChatGPT web | Not available | Not available | Not available | No published app |
A confirmed read records past access, not a live connection check. Passing one column does not verify the others. Separately, a live authenticated MCP read of the writing guide resource succeeded in release 19 from a client that was not recorded; that verifies the server, not any client listed here. Setup guides are also available inside your workspace without JavaScript.
MCP (Model Context Protocol) is the open standard assistants use to call outside tools. Readyweek is an MCP server: once connected, your assistant can read the profile, posts, replies and results you allow, fetch the writing guidance, save a post batch or a reply draft for your review, and upload an image from a file-capable environment. It cannot publish on its own, choose another account, or widen its own permissions. The full tool list is on the MCP and API page.
Sometimes, once. Some clients cache the tool list when they connect, so after a Readyweek update you may need a one-time refresh: reconnect or restart the client to see the new tools. It is not a step you repeat for each draft.
Paste this into the connected assistant. It reads permissions and changes nothing:
Use Readyweek to check my connected Threads account and permissions with threads_get_permissions. Do not draft, publish, or change anything.Your workspace shows the server address for browser sign-in clients and a one-time setup request with a key for terminal clients. A key is shown once; Readyweek stores only a hash. To reconnect a browser sign-in client, open Readyweek in its connector settings and connect again. To revoke an assistant, use Manage access in your workspace: it stops that assistant’s access and leaves your Threads connection in place.
Never give an assistant your Meta or Threads login. The assistant authenticates with its own separate, revocable connection, and Readyweek never returns your Threads credential to it. How that is enforced.