Connect an assistant with MCP

A greeting gets a brief reply and an invitation to say what you would like to work on. It can finish without a plan or saved changes.

Connect your assistant to Knit using Model Context Protocol (MCP). One connection lets it find the Sites you can access and work in the Site you choose. Its work appears in that Site’s Knit Assistant conversation, ready for you to review.

Long assistant conversations open at their newest messages. Choose Load earlier messages to read further back. After 30 days without a new message, Knit automatically retains a private summary with your original request, decisions and unfinished work. A new message restarts that interval. Messages stay available while work is running or a summary cannot be completed. Your saved drafts and pending work remain available.

Preview: Connected assistants can use focused instructions for a question and request detailed writing or formatting guidance when their task needs it.

Preview: Native Knit Assistant can reuse the current source it has kept for an edit instead of restarting inspection after selecting relevant context.

Preview: Connected assistants receive guidance for linking to the source note or personal draft behind an answer.

Preview: Connected assistants receive direct links to the personal drafts they save, including drafts inside folders or another workspace.

Preview: Assistants receive direct links when finding your pending drafts, including when continuing a longer task.

Preview: Source reads tell assistants when personal-draft content has not been inspected, so a published-only read is not mistaken for a missing draft.

Preview: Knit Assistant receives clearer recovery guidance when it needs to record a read-only plan before inspecting pending work.

Preview: Knit Assistant selects the source evidence for its answer before finishing, including after checking a saved edit again.

Connected assistants can continue an exact text edit from a matching search result across tool calls. If the source changes, they must read it again; changes outside the returned passage still need a full current read.

Preview: Connected assistants have clearer guidance for checking saved exact text changes from current matching passages, while keeping the original scope and preserving the rest of each draft.

Preview: Literal-edit guidance prefers matching passages even after the assistant knows which notes to change. It can still read complete drafts when the task needs wider context or search cannot retrieve a requested note.

When current work changes during a connected task, the assistant receives clearer guidance for continuing unfinished work from current sources while preserving saved results and your manual edits. The usual approval still applies to the new plan.

Preview: If changed work interrupts a connected task, Knit keeps the saved drafts and unfinished step visible after reload. Continue in your connected assistant to check the current drafts and finish the remaining work.

Preview: Native Knit Assistant keeps source links available when it selects passages for an answer. Ask for source links to open the notes behind its facts.

Preview: Native Knit Assistant can recover a missed inspection step while answering a read-only question, without asking you to approve changes.

Preview: Native Knit Assistant keeps the source passages needed for a task across several pages. Interrupted work resumes with the same approved plan and saved drafts. The assistant reads the current source needed for further changes and preserves your surrounding manual content.

Preview: Table proposals are checked before saving. If rows do not line up, the assistant receives the affected table and row so it can correct the proposal. An invalid proposal saves no changes to your content.

Preview: When adding a section, Knit Assistant preserves the original headings around unrelated manual tables and lists. Its conversation feedback also accounts for the task steps that have already completed.

Preview: Clearer writing guidance keeps names and conditions with the facts you supply and checks the final account against the saved draft.

Preview: Knit Assistant gets clearer feedback when correcting the source passages it keeps while working across pages.

Preview: In Conversations, your initial request scrolls with the messages. The plan and file review each have their own scrolling area, with the step count and bottom review actions kept visible. On a phone, open the work panel to see both areas.

Connected clients that advertise OpenAI forms receive the saved Knit question in that form format. Approval takes effect only after Knit saves your answer; displaying or selecting an option alone does not approve a plan. If an answer is rejected, the plan stays unapproved and the assistant reports that your decision was not saved.

You need a Knit account, access to the intended Site, and an assistant that supports remote MCP over HTTP with OAuth. Starting a writing task also requires writing permission in that Site.

A public ChatGPT directory listing is not yet available. Use a custom MCP connection with the settings below.

Connection settings

Use automatic OAuth client registration when your assistant offers it. Leave optional client ID and client secret fields empty. Knit handles sign-in and consent in your browser; you do not need to copy a Knit access token or API key.

Connect ChatGPT

Use ChatGPT on the web:

1. Open Plugins, select +, then Add custom MCP server.
2. Name it Knit, enter https://knit.wiki/api/mcp as the server URL, and choose OAuth authentication.
3. Review ChatGPT’s connection notice and create the personal plugin.
4. Open the resulting plugin in your personal plugins and install it. Complete Knit sign-in when prompted, check the account and requested access, then choose Allow connection.
5. Open a new Work chat. Type @ in the prompt box and select Knit.
6. Ask: “List the Knit Sites I can access.” If sign-in appears at this point, complete it, then repeat the request.

The result should list your Sites and their current permissions. If custom MCP connections are unavailable, check your ChatGPT account and workspace policies. See OpenAI’s connection instructions and custom MCP authentication options.

Connect Claude Code

In your terminal, run:

claude mcp add --transport http knit "https://knit.wiki/api/mcp"
claude mcp login knit

Complete the Knit sign-in and consent screen in your browser. Use the Knit account that has access to your Sites, then choose Allow connection.

Run claude mcp get knit to check the connection. Inside Claude Code, /mcp also lets you inspect the server and authenticate. Ask Claude Code: “List the Knit Sites I can access.”

See Claude Code’s MCP connection and authentication instructions.

Choose a Site and try a task

Start with the read-only request “List the Knit Sites I can access.” Check the Site names before asking for changes. Then give a concrete request, such as:

In the Acme Site, create a draft called Friday handover with a checklist for completed work, open decisions and next steps. Leave it for me to review in Knit.

Replace Acme with your Site’s name. To work elsewhere, name the other Site in your next request. You do not need a second connection for a second Site.

Each Site has its own permissions, conversation and selected drafts. Your role may let the assistant write in one Site while preventing writing in another. The assistant checks access for each request and asks when the intended Site is unclear.

Approve the plan

Before making changes, the assistant presents its intended result, destination, wording approach and planned steps. Choose Approve plan to proceed or Change the plan with your comments to request a new proposal. Decline or Cancel leaves the plan unapproved. A revised plan needs its own decision.

In Knit, the question appears inline and the agreed plan stays beside the work. Disconnecting a connected assistant preserves that recorded decision and saved work. A connected assistant uses its standard confirmation interface when supported. If its client cannot show the question, open the linked Knit conversation to answer there, then continue with the connected assistant. Answering in Knit does not switch an MCP task to the native writer. Native answers resume the original task and preserve any separate unsent text. Approval alone creates no drafts; reviewing and publishing the resulting saved work is a later decision.

Answer a question in Knit

For a simple choose-one question, click its option card to send that answer. You can add an optional comment before choosing. Questions that need more information keep their full form. Decline or Cancel leaves the question unanswered. If saving fails, your entered values remain so you can try again.

Continue and review in Knit

Large conversations keep their saved progress as you continue working across pages in Knit Assistant or a connected assistant. Previously read pages do not need to be reopened just to update progress; current edits are checked before changes are saved.

Open the chosen Site in Knit. Its existing conversation appears on For you even when native Assistant writing is unavailable. Choose View conversation for messages and progress, or View changes to inspect the saved drafts. Review the files, then use Knit’s Publish all or review-request controls when you are ready. The connected assistant cannot publish the drafts for you.

While Knit checks the saved drafts, the publish action shows Checking drafts…. An earlier writing run that was cancelled by your edits does not block publishing the current drafts. If the batch cannot start, Knit shows one message and keeps your selection available to retry. The plan panel shows its steps and progress without a separate approval badge.

Replies from a connected model show a small model label when the connection reports its identity and it differs from Knit's configured model. The label identifies the individual contribution, including when you continue in Knit. It says “reported by connection”; Knit does not independently verify that model identity. An unidentified connection shows “Connected assistant”.

You can continue the saved conversation with Knit Assistant when native writing is available. It receives the same stored conversation and selected drafts, then reads the current pages before editing. Later connected-assistant instructions also continue that Site’s current conversation. Your external chat transcript is not automatically imported.

Independent tasks can work in separate conversations at the same time. A draft selected by another conversation stays protected. A successful retry can complete a task while preserving the earlier failed attempt in its work history.

Open Conversations to choose an open topic or start New conversation. Switching topics preserves unsent input and saved work while an active task continues. A draft selected by another topic stays protected; open its owning conversation to review the work, remove that draft from its selection, or finish it before including the draft elsewhere.

The list loads recent conversation records first. Select Load older for the next page. Earlier messages inside an open conversation load separately on demand. Finished records offer Follow up, which opens an empty composer with the retained summary as background. Finish conversation preserves saved work, with Stop and finish when a task is running.

When the connected task finishes and native writing is available, the same conversation’s chatbox becomes ready for your next request.

If native writing is unavailable or your Site has reached its writing allowance, the chatbox is disabled. You can still review and publish saved drafts with your usual permissions. The finished conversation records the saved changes and confirmed file outcomes, including when the connected assistant did all the writing.

Requested organization and review actions can take effect immediately and appear in the conversation’s work record.

For a transfer between workspaces, review the exact pages, destination and access change in Knit before confirming. A confirmed move is recorded in the shared Assistant plan so either assistant can verify it and continue the conversation.

Connect only one Site

To limit a connection to one Site, open Settings → Account → Your connected assistants in Knit and copy the Site address shown there. Use that address instead of https://knit.wiki/api/mcp when adding the connection. Check the Site on the consent screen before choosing Allow connection.

Existing Site connections continue to work. The connection uses your Knit account; it does not require a separate “Sign in with ChatGPT” account.

Troubleshoot or disconnect

• Knit is not available in your ChatGPT chat: check that you installed the personal plugin, then select it with @ in a Work chat.
• A Site is missing or writing is refused: check the signed-in Knit account and your current Site permissions. Ask a Site administrator if access needs to change; reconnecting does not grant membership.
• A workspace or destination needs another check: the assistant checks the current workspace and destination before retrying. Saved work stays in place; a refused change has not been applied.
• An answer is saving: wait for the saved answer and confirmed result. If saving fails, your choices and entered text stay available to retry.
• The connection expired or was disconnected: reconnect from your assistant and repeat Knit sign-in and consent. Your saved drafts remain in Knit.

To disconnect, open Settings → Account → Your connected assistants and choose Disconnect beside the assistant. An account connection is labelled Across the Sites you can access; disconnecting it stops that connection across your Sites. A Site connection is labelled This Site only and stops only that connection. Separate Site connections must be disconnected separately.

Each person manages their own connections. Disconnecting preserves the saved Knit conversation and drafts.