MCP handover between Claude and ChatGPT
MCP handover between Claude and ChatGPT moves a job through a shared handover link rather than requiring a client to reconstruct two separate chats.
Try the Zambo demo · Explore Zambo
Ask Claude to hand over its work with Zambo. Open the handover and choose "Continue this job in another AI". Copy that prompt into ChatGPT. When ChatGPT hands over the next part, it links back to the work it picked up. Your client gets one link showing every hop and its receipts.
A pasted chat summary can help the next AI understand a task, but it does not preserve the record of what ran. A handover carries the saved steps and the things the producer did not check. The next part gets its own record without changing the earlier one.
Both AIs need Zambo connected to pick up and publish the work. The client does not. The client opens a normal page and can review the steps before choosing Accept or Flag a problem through the client link.
On jobs with more than one hop, "How this job moved" lists the parts in order. AI names are reported by the AI, not matching. Private parts appear as private, without a link that reveals their contents.
Prompt: continue the work
Open the first handover and use its copy button for the prompt that includes your job's link. Tell the next AI what you want it to do next. Do not send an owner link to the client.
"Continue this job using Zambo. Pick up the earlier handover, do the next part, then hand it over as a continuation. Keep the earlier receipts unchanged and say what you did not check."
Worked example
Claude prepares a draft and publishes a handover. You open it and copy the continuation prompt into ChatGPT to review the draft. ChatGPT picks it up, records its review, and publishes the next handover linked to the first. The client sees the draft and review as separate parts. An accepted decision records the decision of the holder of the client link, not that either part is correct.
Technical details
Call handover_accept for the earlier handover. In that same job session, call handover with continue_from set to the earlier handover id. A chain supports up to 25 hops. Read the chain in acceptance.json or handover_status. Receipt reference: draft-zambo-aer1-26.
Frequently asked questions
Does the client need an AI account?
No. The client opens the handover link in a browser. Accept and Flag need the separate client link.
Are the AI names matching?
No. AI names are reported by the AI, not matching. Receipts check saved bytes, not identity or accuracy.
Can I keep the earlier work unchanged?
Yes. The next handover links to the earlier one. It does not rewrite the earlier receipts.
By Brennan Zambo, founder of Zambo.
Last updated: 2026-10-18.
Keep going with Zambo in your AI
For developers
Get receipts for your own AI work. Add one link, then ask in plain English.
A three-step handover
- Start the job in Claude and ask Zambo to save the work in a handover.
- Open the handover in a connected ChatGPT session, inspect the context, and continue the work.
- Give the client one handover link so they can inspect receipts and Accept or Flag the delivery.
ChatGPT requires a paid plan for a custom connector.
A three-step handover
- Start the job in Claude and ask Zambo to save the work in a handover.
- Open the handover in a connected ChatGPT session, inspect the context, and continue the work.
- Give the client one handover link so they can inspect receipts and Accept or Flag the delivery.
ChatGPT requires a paid plan for a custom connector.
A three-step handover
- Start the job in Claude and ask Zambo to save the work in a handover.
- Open the handover in a connected ChatGPT session, inspect the context, and continue the work.
- Give the client one handover link so they can inspect receipts and Accept or Flag the delivery.
ChatGPT requires a paid plan for a custom connector.
A three-step handover
- Start the job in Claude and ask Zambo to save the work in a handover.
- Open the handover in a connected ChatGPT session, inspect the context, and continue the work.
- Give the client one handover link so they can inspect receipts and Accept or Flag the delivery.
ChatGPT requires a paid plan for a custom connector.
A three-step handover
- Start the job in Claude and ask Zambo to save the work in a handover.
- Open the handover in a connected ChatGPT session, inspect the context, and continue the work.
- Give the client one handover link so they can inspect receipts and Accept or Flag the delivery.
ChatGPT requires a paid plan for a custom connector.
Try a handover
A handover gives your client one proof link with verifiable receipts to review, then Accept or Flag.
try it: say 'use zambo to hand this over to <client>' in your ai
A three-step handover
- Start the job in Claude and ask Zambo to save the work in a handover.
- Open the handover in a connected ChatGPT session, inspect the context, and continue the work.
- Give the client one handover link so they can inspect receipts and Accept or Flag the delivery.
ChatGPT requires a paid plan for a custom connector.
What this evidence means
A receipt shows whether the recorded result matches its saved fingerprint and has not changed after the fact. It does not prove the answer is right or authenticate the issuer's identity. AER-1 is an open draft spec.
Explore related work
A three-step handover
- Start the job in Claude and ask Zambo to save the work in a handover.
- Open the handover in a connected ChatGPT session, inspect the context, and continue the work.
- Give the client one handover link so they can inspect receipts and Accept or Flag the delivery.
ChatGPT requires a paid plan for a custom connector.