Poke texts you. The person it is for needs a link.

Add Stacktree to Poke

Poke takes any remote MCP server as an integration, and Stacktree's is at https://api.stacktr.ee/mcp. Poke's docs describe a prefilled link with three optional parameters: name, url and apiKey. This one fills in the first two:

https://poke.com/integrations/new?name=Stacktree&url=https%3A%2F%2Fapi.stacktr.ee%2Fmcp

Add Stacktree to Poke →

Create the integration and Poke connects and lists Stacktree's tools. Poke's docs say a server that supports OAuth with dynamic client registration signs in automatically when it is added this way, and Stacktree's server does, so you sign in to Stacktree once and approve. The same works from a terminal:

npx poke@latest mcp add https://api.stacktr.ee/mcp -n "Stacktree"

If you would rather use a key, create one at app.stacktr.ee/api-keys, name it Poke, and paste it into the API key field (or add -k and the key to the command). Poke sends it as Authorization: Bearer on every request, which is how Stacktree reads a key, and you can revoke it from the same page.

One thing to know: we have not run this inside Poke ourselves yet. The steps come from Poke's documentation, and the server is the same one Claude, ChatGPT, Grok Bot and Cursor already connect to. If it does not work for you, tell us.

What to ask Poke for

Name the thing, who it is for, and ask for the link back before anyone else gets it:

Turn our Lisbon plan into one page for the six of us:
flights, the flat, a day-by-day, and who owes what.
Publish it privately to Stacktree and text me the link.

Make the Q4 proposal for Dana at Northwind a single
page, with a passcode, and publish it to Stacktree.
Send me the link and the passcode before you share it.

Every Friday, update the weekly report page you already
published on Stacktree with this week's numbers.
Same link. Tell me what changed.

The last one matters most for anything that repeats. Stacktree replaces a page at the same address, so the link the reader already has shows the new version, and nobody compares two copies. Say "update the page you already published", not "publish a new one".

Why a private page, not a message or a site

Poke can build and deploy a website for you at yourname.poke.com. Its docs do not describe a passcode, a separate link for each person, word of when someone opened it, or a way for the reader to comment. Those are what a page meant for one person needs, and they are what Stacktree is for:

• An unguessable link that is never listed or indexed, with a passcode available on every plan.
• On Solo and up, a link with the reader's name on it, so you see when they opened it, with an email the first time they do.
• Comments on the page itself, with no account for the reader, when you switch them on.
• The current version every time, at the same address.
• A preview card when the link is pasted into Apple Messages, WhatsApp, Slack or Discord.

No integration at all

Any agent that can make an HTTP request can publish with no account and no integration. One call returns the private link, an expiry 24 hours away, and a token that updates the page in place:

curl -X POST https://api.stacktr.ee/sites \
  -H 'content-type: application/json' \
  -d '{"html":"<!doctype html>...","owner_email":"you@example.com","agent":"poke"}'

owner_email is you, given with your permission: Stacktree emails you the link that keeps the page, and once more the first time someone else opens it. Poke's docs do not say whether it makes arbitrary web requests itself, so treat this as the route for other agents and the integration above as the route for Poke. The three calls (send, ask whether it was opened, update) are on the agents page.