Logo
Apdf tutorials October 2026 3 min read

How to Mint PDF Tracking Links from ChatGPT

The moment you decide to share a document is rarely a browser-tab moment — it's mid-conversation, drafting the email in whatever assistant you already have open. Breaking away to a dashboard to mint the link is exactly the friction that makes people fall back to attachments.

The Apdf MCP server speaks to any MCP client — and that includes ChatGPT. Connect it once and sharing a tracked PDF becomes part of the conversation you were already having.

What you'll build
A tracked, revocable, personal link minted from inside ChatGPT: “Share the pricing guide with Elif” → her personal URL, pasted into the draft you were writing
MCP access needs Pro (14-day trial, no card)
1

Connect ChatGPT to Apdf

One endpoint serves every MCP client:

https://apdf.io/mcp/main

In ChatGPT, add it as a connector (Settings → Connectors — custom MCP connectors live behind developer mode on plans that support them), sign in when the OAuth window opens, and the Apdf tools appear in the conversation. The same URL works in Claude, Cursor and Gemini — connect them all; the workspace doesn't care who's asking.

2

Share without leaving the draft

You
I'm writing the intro email for Elif Demir (elif@demirstudio.example) — share the 2026 pricing guide with her and put the link in the draft.
Claude
apdf · create-document-link
Done — Elif has her own tracked link now, and I've dropped it into the draft. When she opens it, her visits will show up under her name.

The create-document-link tool returns the URL and its metadata — this is the actual payload:

{
    "token": "aLo58OJu",
    "name": "Elif Demir",
    "email": "elif@demirstudio.example",
    "url": "https://docs.apdf.io/studio/688b0-07ba8-42bc4?v=aLo58OJu",
    "is_active": true,
    "last_viewed_at": null,
    "created_at": "2026-07-23T09:17:50.000000Z"
}

That's a real link with everything attached: attribution (Elif's sessions carry her name), analytics (pages, dwell, returns), and a kill switch you'll meet in a moment.

3

The rest of the lifecycle, same chat

Sharing is the write side's first verb, not its last:

You
Did Elif open it yet? And kill Dana's old link on the Q3 proposal — she left ClientCo.
Claude
apdf · list-document-links, deactivate-document-link
Not yet — Elif's link shows no view so far; I'd give it until tomorrow before nudging. Dana's link is deactivated: it now lands on a 403, while her past reading history stays in your analytics.
{
    "token": "YGY35sNP",
    "name": "Dana Whitfield",
    "email": "dana@clientco.example",
    "url": "https://docs.apdf.io/studio/4352c-99928-25aa1?v=YGY35sNP",
    "is_active": false,
    "last_viewed_at": null,
    "created_at": "2026-07-23T07:48:05.000000Z"
}
Tip: The toolbelt behind the chat covers the whole document lifecycle — upload, links, sessions, analytics, revocation, archiving — plus every PDF operation. What your assistant can do is the same list, regardless of which assistant it is.

Where to go from here

Once the assistant can share, teach it to read the signals too.

Ready to see who reads?