MCP setup

Connect Dealpages to your agent

One endpoint, one key, one command. Dealpages is a remote MCP server over Streamable HTTP — nothing to install or run locally, no Node, no npm.

1 · Get a key

Sign in with your email — no password, just a link. On your account page, press Create new key and copy it. Keys are shown once; revoke and re-create anytime. (Using claude.ai? Skip this step — it signs you in instead.)

2 · Connect your client

claude.ai (web and desktop app)

No key needed. Settings → Connectors → Add custom connector → URL https://app.dealpages.app/mcp. Claude sends you to Dealpages to sign in with your email and press Allow; that's it. Disconnect any time from the Connected apps list on your account page.

Claude Code

claude mcp add dealpages --transport http https://app.dealpages.app/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Restart your session after adding. Your account page renders this command with your real key filled in. (Claude Code can also connect without a key — run the command without the header and it will open the sign-in page.)

Codex

Add to ~/.codex/config.toml — Codex reads the key from an environment variable rather than the config file:

[mcp_servers.dealpages]
url = "https://app.dealpages.app/mcp"
bearer_token_env_var = "DEALPAGES_API_KEY"

Then set export DEALPAGES_API_KEY=your_key in your shell profile so it's present when Codex launches.

ChatGPT

Settings → Connectors → Advanced → Developer mode, then add a connector with the URL https://app.dealpages.app/mcp and the Authorization: Bearer YOUR_API_KEY header.

Any other MCP client

Standard MCP over Streamable HTTP at https://app.dealpages.app/mcp. Two ways in: a bearer header carrying your API key, or OAuth 2.1 — the endpoint advertises its authorization server the standard way, so any client that supports remote MCP sign-in (PKCE, dynamic or metadata-document client registration) can connect with no key at all.

3 · Verify it's connected

Ask your agent:

List your dealpages tools.

You should see the 14 tools below. Prefer a terminal check? This returns your email:

curl https://app.dealpages.app/api/whoami \
  -H "Authorization: Bearer YOUR_API_KEY"

The tools

What your agent can do once connected. You never call these yourself — you ask in plain language ("publish a recap page for Acme") and the agent picks the right tool.

Tool	What it does
`publish_page`	Publish a complete HTML document as a live page; returns the URL.
`update_page`	Publish a new version of an existing page — every shared link shows it immediately.
`list_pages`	All your pages with state, version, and link counts.
`get_page`	One page's details: links, sections, warnings, optionally the current HTML.
`mint_link`	Create a tracked link for one stakeholder (the per-person URL you actually share).
`list_links`	Every link for a page, with URLs and a ready-to-paste share line per stakeholder.
`revoke_link`	Kill one stakeholder's link (wrong inbox, left the deal) without touching the page. Reversible.
`get_engagement`	What happened since you last asked: who read what, for how long, new-viewer signals, comments.
`list_feedback`	Buyer comments with their anchors and status.
`resolve_feedback`	Mark a comment handled (usually after updating the page).
`set_password`	Password-protect a page (or clear it).
`set_expiry`	Auto-expire a page at a time you choose.
`unpublish`	Take a page offline immediately (reversible).
`republish`	Bring an unpublished page back at the same URLs.

Optional: install the publishing skill

A skill teaches your agent Dealpages' conventions — section tagging for analytics, one link per human, honest engagement language — plus the starter templates. Everything works without it; pages are just less consistently good.

The skill is a small folder of plain files that goes in ~/.claude/skills/. It isn't publicly downloadable yet — if you got your key from Kyle, ask him for the folder. A download link will live here once it's packaged.

Troubleshooting

401 / "Invalid or revoked API key" — the key was mistyped, revoked, or replaced. Check your account page; revoking a key disconnects everything using it immediately.
Tools don't show up in the client — restart the client session after adding the server. In Claude Code, claude mcp list should show dealpages as connected.
"HTML must be a complete document" — the publish tools take full documents (<html> + <body>), not fragments. Agents handle this automatically; you'll only see it if the agent sent a snippet.
Published fine, but engagement is empty — visits to the preview URL are deliberately never counted (it's your own untracked view). Share the per-stakeholder links from mint_link; those are what's measured.
No Node version to worry about — this is a remote server; the only local requirement is an MCP client.