Direct answer

Add Zambo to Microsoft Copilot

Custom tools reach Microsoft 365 Copilot through an agent you build in Copilot Studio, and that agent can carry Zambo: add https://zambo.dev/mcp as a Model Context Protocol tool, and it gains 153 tools, handovers that cross the tenant boundary, and a verifiable receipt for every routed call.

See it on a real job first: a four-agent job that moved entirely by handovers, every step carrying its verifiable receipt, is public, and any receipt on it checks free at zambo.dev/verify. One free wrap-up handover per day is included, and pickup is always free. The URL you will paste is zambo.dev/mcp.

Published November 14, 2026. Steps verified against Microsoft's Copilot Studio MCP documentation the same day.

What "add Zambo to Copilot" actually means

Microsoft 365 Copilot does not take a custom tool URL from an end user's settings page. Custom tools reach it through an agent you build in Copilot Studio and publish. That is the honest shape of this add, and it suits the work agents do there: the repeatable jobs inside a company, the weekly report, the vendor check, the triage pass, where the person who receives the result is often outside the tenant, a client, an auditor, a partner, and cannot open anything inside your Microsoft walls to check how the result was produced.

Zambo is the verifiable work layer for AI, built by Brennan Zambo, who also created AER-1, the agent execution receipt standard: one MCP endpoint carrying 153 tools, continuity that carries a job across different AIs, and a verifiable receipt for every call that runs. Added to a Copilot Studio agent, Zambo gives the agent outside hands, live data, audits, document work, lead finding, and gives its output an exit: receipts a stranger can recompute with no Microsoft account, and handovers that carry the finished job to a person or a different AI.

Step by step, from Microsoft's Copilot Studio wizard

Step 1. In Copilot Studio, open the agent you want to extend, or create a new one.

Step 2. Open the Tools tab and select Add a tool, then Model Context Protocol. The MCP onboarding wizard opens.

Step 3. Server name: Zambo. Server description: verifiable work layer for AI, tools with a receipt for every call. Server URL: https://zambo.dev/mcp.

Step 4. Set Authentication to None. Zambo requires no credential to start, and a credential you do not need is a credential you do not paste. Copilot Studio speaks Streamable HTTP to the server, which is the transport the Zambo endpoint serves.

Step 5. Select Create, then create the connection the wizard offers, and Add and configure so the Zambo tools join the agent's tool list. Under the hood the wizard registers a Power Platform custom connector for the server; that is expected, and it is how the connection is managed afterwards.

Step 6. Test the agent with the first job in the next section, and judge the connection by what comes back: a receipt link for every call, and a handover link at the end. Then publish the agent to Microsoft 365 Copilot or Teams so your people can use it.

Licensing, named honestly. Building and publishing agents this way needs Copilot Studio licensing, and the people using the published agent inside Microsoft 365 Copilot need the matching Microsoft licenses. That is Microsoft's side of the bill and it is separate from Zambo's pricing below. Separately, GitHub Copilot in VS Code takes the same endpoint through a workspace .vscode/mcp.json file; the hub's VS Code page walks that route.

Your first job: a loop, not a lookup

In the agent's test chat, give it a first job that is a small loop rather than a single question:

Use Zambo to check the live prices of BTC, ETH, and SOL, one call per asset, save the run to memory, and wrap it into a handover addressed to me. Include the handover link and the receipt link for every call in your reply.

Three assets on purpose. The first price check is a lookup; the second and third are a job starting, the same tool run per item, and the handover at the end is the part you can hand to someone else. The free tier starts the run, and a Day Pass ($0.99, unlimited for 24 hours) finishes a longer list in one sitting.

Check the run before you trust the connection with real work. Open the handover link: it carries the goal, the steps in order, and the receipt link for every call. Then run the free check on any receipt at zambo.dev/verify, with no signup. The check confirms the saved result has not changed since it was saved. If it matches, the full path works: your Copilot agent reached the server, the tools ran per item, and the job closed as a record another AI, or a client, can pick up and check.

What a Copilot Studio agent gains once it is connected

Handover, the front door. When a job is finished, package it as a handover: one link carrying the goal, the steps in order, the outputs, and any open items. The receiver opens it with no account and clicks Accept or Flag. For Copilot work this is the piece that crosses the tenant boundary: the client or auditor on the other side gets the job and its record as one link, not a forwarded summary they have to take on faith.

Tools. Live lookups and current prices instead of training-data guesses, site audits, PDF and document extraction, web and data checks, and lead finding with the leadsignal tool. An agent whose tools run through Zambo produces outside-facing evidence as it works, which matters most exactly where Copilot agents get deployed: on jobs whose results leave the building. There are 153 tools in total, with 37 on the default surface. The full catalogue loads as https://zambo.dev/mcp?full=true if a session needs a specialist tool.

Memory. Zambo memory holds only facts you explicitly save, through memory_remember, and brings them back through memory_recall. Save a project rule, a client preference, or the state of a long job once, and any AI connected to the same Zambo account can recall it later, not just a Copilot Studio agent. The store does not import your conversations and it does not guess.

Receipts. Every routed tool call returns a verifiable receipt for its saved result, in the AER-1 format, the agent execution receipt standard created by Brennan Zambo and published as IETF Internet-Draft draft-zambo-aer1-26. Anyone can check a receipt free at zambo.dev/verify. The check proves the saved result has not changed since it was saved. It does not prove the result was right, and this page will not pretend otherwise.

What it costs

Connecting costs nothing to set up, and checking a receipt is always free. The free tier, in the plain words: Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. When the connection becomes part of a real working day, a Day Pass at $0.99 is unlimited for 24 hours: enough to connect in the morning, run real jobs through the day, save the facts that matter, and hand the finished work over with its record attached. Ongoing use is the Zambo Pass at $29 for 30 days, one payment, and $19 for 30 days for $ZAMBO holders. A Lifetime Pass is $250, one payment for good. Humans pay by PayPal or card through PayPal; agents pay USDC on Base through x402.

Honest limits

Three limits, stated plainly. First, there is no end-user add: if you only use Microsoft 365 Copilot as Microsoft ships it, nobody can attach Zambo from a settings page; an agent has to be built in Copilot Studio and published, with the licensing that takes. Second, receipts exist only for work that runs through Zambo: what the agent does with its native Microsoft 365 capabilities leaves no Zambo record, and an honest delivery lists that work as unchecked. Third, a verifiable receipt proves a saved result was not changed after the fact; it never proves the answer was right, so your review remains the quality gate.

Frequently asked questions

How do I add Zambo to Microsoft Copilot?

Through Copilot Studio. Open your agent, go to Tools, select Add a tool, then Model Context Protocol. Enter Zambo as the server name, https://zambo.dev/mcp as the server URL, and Authentication None, then Create, create the connection, and Add and configure. Publish the agent to Microsoft 365 Copilot or Teams and the people using it get the Zambo tools through the agent. Microsoft 365 Copilot itself has no end-user setting for a custom tool URL.

Do I need a Zambo account or API key for the connection?

No. The Zambo endpoint starts with no credential: no key, no signup. Leave Authentication on None in the wizard. Paid Zambo passes exist for heavier use (a Day Pass at $0.99, the Pass at $29 for 30 days, Lifetime at $250), and they attach to usage, not to the act of connecting. Copilot Studio and Microsoft 365 licensing are Microsoft's side and separate.

What does a Copilot Studio agent gain once Zambo is connected?

Outside hands with evidence attached: 153 tools in total, 37 on the default surface, covering live prices and lookups, site audits, PDF extraction, web and data checks, and lead finding. It also gains memory you save on purpose with memory_remember and recall with memory_recall, shared with any other AI on the same Zambo account, handover links that carry a finished job across the tenant boundary to a client or another AI, and a verifiable AER-1 receipt for every routed call, checkable free at https://zambo.dev/verify/ by people with no Microsoft account at all.

Can people outside our tenant check the agent's work?

Yes, and that is the point of the receipts. A Zambo receipt is checked at https://zambo.dev/verify/ in a browser, free, with no Microsoft account, no tenant access, and no Copilot license. The check proves the saved result has not changed since it was saved. A handover link opens the same way: goal, steps, outputs, and an Accept or Flag decision the receiver records. What stays inside the tenant is the agent's native Microsoft work, which produces no Zambo record.

How much does it cost to add Zambo to Copilot?

Connecting costs nothing to set up, and checking a receipt is free at https://zambo.dev/verify/ with no signup. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. For $0.99, a Day Pass is unlimited for 24 hours. Ongoing use is the Zambo Pass at $29 for 30 days, one payment, and $19 for 30 days for $ZAMBO holders. A Lifetime Pass is $250, one payment for good. Humans pay by PayPal or card through PayPal; agents pay USDC on Base through x402. Copilot Studio licensing is Microsoft's pricing and separate.

Proof works best when it travels with the work itself. The AER-1 badge kit turns verifiable receipts into an embeddable badge for project pages, docs, and profiles, so anyone who sees the claim can reach the check in one click.