By · Founder, Stacktree · Last updated
Personal Agent Protocol · MCP

Personal Agent Protocol vs MCP.

They are not rivals. MCP is how an agent calls your tools. The Personal Agent Protocol, Poppy for short, is how an agent you have never heard of finds your company, proves who it is and gets its person's approval before that call. Stacktree serves both on one endpoint, so this is the comparison with the wiring showing.

The Poppy Simulator calls our MCP server over a Poppy Session.

What is the difference between the Personal Agent Protocol and MCP?

MCP (Model Context Protocol) standardizes how an AI agent lists a server's tools and calls them. The Personal Agent Protocol (Poppy) standardizes what comes before the call when the agent belongs to a member of the public: finding the company from its domain, proving which agent is asking, tying requests to one person, and getting that person's approval on the company's own page. Poppy lists MCP as one kind of API a company can offer, so most companies with an MCP server keep it and add a poppy.json that points at it.

Side by side

The Poppy column is from the 1.0 spec, published 14 November 2026.

Question MCP Personal Agent Protocol
What does it standardize? Listing a server's tools and calling them How a person's agent and a company meet: discovery, identity, Sessions, sign-in
How does an agent find you? It is given your server's address, by a person or a directory It fetches /.well-known/poppy.json from your domain
How does the client say who it is? Through MCP's OAuth flow, when the server asks for sign-in On every request, signed out too: a signed Poppy-Session header tied to a metadata URL it publishes
Who is the person? Whoever signed in A stable, pseudonymous User ID per company before sign-in, and the account after
What can the agent reach? The MCP server APIs (MCP or OpenAPI), your website in a browser, and your own support agent
Who defines the tools? MCP does: schemas, results, errors Nobody. The spec "leaves each API's schema to that API"
When you cannot help? A tool error A list of tasks you chose not to offer, and a feedback endpoint for what was asked

What the spec says about MCP

Section 7 of the spec defines two API types a company can list: openapi and mcp. The MCP rules are short:

  • Which MCP. A remote server on the Streamable HTTP transport, MCP version 2025-06-18 or later.
  • Sessions are separate. "Poppy Sessions are independent of MCP's transport lifecycle." Whether the server uses the older initialize handshake or the per-request metadata of MCP 2026-07-28, the agent sends the same Poppy-Session header. The guides add that the Session's id "is not an Mcp-Session-Id".
  • Signed out works. A server that accepts the Session header can take signed-out calls with the header only, if it allows them.
  • Tokens are for one server. A signed-in agent asks for a token with resource set to the MCP server's address from poppy.json. That token works only there.
  • Other MCP clients are untouched. Clients that do not implement the protocol "sign in with MCP's own authorization flow, outside this protocol, and their requests belong to no Session".

One endpoint, both protocols

Here is the entry in our live poppy.json, with the description shortened:

"apis": [
  {
    "type": "mcp",
    "url": "https://api.stacktr.ee/mcp",
    "description": "Publish a page to a private link that opens with no account, update it in place, see who opened it and what they commented."
  }
]

And here is a personal agent that has never contacted us before, listing our tools signed out:

POST https://api.stacktr.ee/mcp
Poppy-Session: eyJ0eXAiOiJwb3BweS1zZXNzaW9uK2p3dCIs...
Poppy-Version: 1.0
Content-Type: application/json

{ "jsonrpc": "2.0", "id": 1, "method": "tools/list" }

That is an ordinary MCP request with two extra headers. The same address serves the Claude and ChatGPT connectors, which send neither header and sign in through MCP's own OAuth flow. Three things are shared between the two paths: the tools, the two scope names (sites:read and sites:write), and the consent page a person sees. One middleware in front of the server checks the Session header when there is one.

What Poppy adds that MCP leaves open

  • Discovery from a domain. A person tells their agent "return this to Example" and the agent starts from example.com. Nobody has to install a connector first.
  • An identity for agents nobody registered. The agent's client_id is the address of a metadata document with its name and keys (section 4.1). You can tell a customer's agent from a scraper on the first request, and block or rate-limit one agent without touching the rest.
  • A person before sign-in. The User ID is stable for one person at one company and different at every other company (5.1). You can keep a cart or a draft for a signed-out person and still not know who they are.
  • Rules for the consent page. It is your page, it names the agent, and since 1.0 it lists every scope every time. Device Sign-In has its own rules for agents with no browser.
  • The website and your own agent. A browser can join the Session and use your site signed in without the token passing through it (section 6). A personal agent can talk to your support agent and be handed to a person (section 8).
  • A way to say no. Tasks you chose not to offer, and feedback when a person asked for something you cannot do (section 9).

What MCP does that Poppy does not

  • The call itself. Tool schemas, results, resources, prompts, and asking the person a question in the middle of a tool. Poppy has none of this and does not try to.
  • Clients people already use. Claude, ChatGPT and most coding agents connect to MCP servers today. A person adds your server once and uses it from then on. Poppy is five weeks old, and Sierra says its first large agent, Meta's Muse, switched it on this month.
  • Private and internal use. An MCP server can sit behind a company's firewall for its own staff. Poppy is about the public: a company and the agents of people it has never met.

Which do you need?

  • You have an MCP server. Add a poppy.json that lists it. For signed-out use that is one static file and letting two headers through. Our field guide has the smallest valid file.
  • You have a REST API and no MCP server. You do not need MCP for Poppy. List your OpenAPI description instead. Build an MCP server when you want to be in Claude or ChatGPT, which is a separate decision.
  • You have neither. Ask who you want to serve first. People who will set up a connector once and keep it: MCP. Agents that arrive at your domain unannounced on a person's errand: Poppy, and its web channel can be the whole of your first version.
  • You build agents. Speak both. Poppy tells you where a company's MCP server is and how its person signs in. MCP is still how you call it.

Three things that bite when you add Poppy to an MCP server

All three are from our own move, written up in our implementation report.

  • Protected resource metadata on a shared host. Our MCP server and our REST API share api.stacktr.ee. The metadata document at the host's root named the MCP server as its resource, because that is where MCP clients were sent. A personal agent reads that same root document before calling the REST API, and would have asked for the wrong token. The root document has to name the host. The MCP server gets its own document at /.well-known/oauth-protected-resource/mcp.
  • One token does not fit both APIs. A token asked for with the MCP server as its resource must be refused everywhere else. If your REST API and MCP server accepted the same token before, they cannot for personal agents.
  • Do not break your connectors. The authorization server is shared, so every Poppy change is a risk to Claude and ChatGPT sign-in. We left DPoP out of our issuer's metadata for that reason, which 1.0 allows, and we keep a test that runs the connectors' OAuth flow with Poppy switched on.

And UCP?

The Universal Commerce Protocol covers catalog search, carts and checkout. Poppy has an optional UCP extension, co-written with Shopify according to Sierra, that connects its discovery and sign-in to UCP. It shows in the wild: every Shopify store we checked on 15 November lists a UCP endpoint in its poppy.json and no MCP server. So the pattern is the same for commerce as for tools. Poppy is the front door, and the protocol behind it depends on the job. Our tracker has the files we read.

FAQ

Frequent questions

Does the Personal Agent Protocol replace MCP? +
No. The Personal Agent Protocol names MCP as one of the two kinds of API a company can list, next to OpenAPI. It does not define tools or how to call them. A company with an MCP server keeps it and adds a poppy.json that points at it.
What is the difference between Poppy and MCP in one sentence? +
MCP standardizes the call: how an agent lists a server's tools and runs one. Poppy standardizes the meeting: how an agent finds a company from its domain, proves which agent it is, acts for one person, and gets that person's approval on the company's own page.
I already have an MCP server. What do I need to add for the Personal Agent Protocol? +
Publish /.well-known/poppy.json on your main domain with an apis entry of type mcp that points at the server, and let requests that carry a Poppy-Session header through. That covers signed-out use. For account access, your authorization server also has to accept agents identified by a metadata URL.
Does an MCP server have to verify the Poppy-Session header? +
It has to accept the header, not always verify it. A server that uses nothing from the Session can serve signed-out calls or rely on an access token alone. It must verify the header before it relies on the Session for identity, ownership or state, such as a cart or a conversation.
Is a Poppy Session the same as an MCP session? +
No. The spec says Poppy Sessions are independent of MCP's transport lifecycle, and the guides say the Session's id is not an Mcp-Session-Id. A Poppy Session is one person's activity at one company through one agent, across APIs, the website and conversations.
Can Claude or ChatGPT connectors still use my MCP server after I add Poppy? +
Yes. MCP clients that do not implement the Personal Agent Protocol sign in with MCP's own authorization flow, and their requests belong to no Session. On Stacktree one endpoint serves the Claude and ChatGPT connectors and personal agents, with the same two scopes and the same consent page.
Which MCP versions does the Personal Agent Protocol work with? +
Version 1.0 asks for a remote MCP server on the Streamable HTTP transport, MCP version 2025-06-18 or later. It covers both lifecycles: the older initialize handshake, and the per-request metadata of MCP 2026-07-28. Both carry the Poppy-Session header the same way.
How does the Personal Agent Protocol relate to UCP? +
UCP, the Universal Commerce Protocol, covers catalog search, carts and checkout. Poppy has an optional UCP extension that connects its discovery and sign-in to UCP. The Shopify stores we checked list a UCP endpoint in poppy.json and no MCP server.
Keep reading

Related guides

References

Sources and further reading

One MCP server, reachable both ways.

Stacktree turns what an agent makes into a private page its person can share. Add it as a connector in Claude or ChatGPT, or let a personal agent find it from our domain. Free to start, no card.

Sign up free →