CertFusion Now Speaks MCP: Issue Certificates from Claude, ChatGPT, or Any AI Assistant

Today we're launching the CertFusion MCP server — a native Model Context Protocol endpoint that plugs your certificate workflow directly into the AI assistant you already use.

https://certfusion.com/mcp

Paste that URL into Claude as a custom connector, or into ChatGPT as a custom plugin, authorize once, and your assistant can run your certificate admin for you. This works today:

You: add David/hi@staticmaker.com to the "Online Webinar" list, then issue the certificate.

Your assistant: Done — David was added, the certificate is issued, and it's already in his inbox.

Why we built this

Certificate admin has a particular shape: it's not hard, it's repetitive. Export a list, upload it, map the columns, click issue, repeat next cohort. We've spent years shaving steps off that loop — Zoom and Webex imports, Typeform and Tally webhooks, a Zapier library, a REST API.

MCP is the step where the loop disappears entirely. Instead of you going to the tool, the tool comes to wherever you're already working. If your day runs through a chat window, your certificates now do too. No tab-switching, no forms — you describe what you want, and the assistant does it against your live CertFusion account.

The unlock is that MCP is an open standard. We built the server once, and it works with every MCP-compatible client — Claude and ChatGPT today, and whatever you're using next year.

What your assistant can do

The server exposes eight tools spanning the whole workflow:

• Browse — list your certificate designs and their recipient lists
• Add — create a recipient from a name and email, or paste in a whole cohort at once with the bulk tool
• Issue — generate the certificate and email it to the recipient, with its QR code and verification URL
• Track — check a recipient's status, list or search recipients across your lists, and ask "is my quota enough?" for live monthly usage

And because it's conversational, the tools compose. "Add these 30 people, but only issue to the ones with a company email." "Who on the March list hasn't been issued yet?" That flexibility is something a fixed integration UI can't give you.

Guardrails, on purpose

Handing write access to an AI raises a fair question: what stops it from blasting certificates to the wrong people? We made three deliberate design calls:

1. OAuth-scoped access. The connection is authorized per-account with OAuth 2.1 — your assistant sees only your own designs, lists, and recipients, never anyone else's.
2. Drafts first. New recipients are always created as drafts. Issuing is a separate, explicit action — nothing goes out because a model got ahead of itself.
3. You control the permissions. Clients like Claude let you set each tool to "always allow" or "ask every time." Leave the write tools on ask, and every issuance needs your click.

Certificates issued through MCP share your normal monthly quota — no separate metering, no surprises on the invoice.

Get connected in five minutes

Setup is a paste-URL-and-authorize affair, and we've written it up for both clients with full screenshots:

• Claude — step-by-step guide · 2-minute video
• ChatGPT — step-by-step guide · 3-minute video (heads-up: custom MCP plugins live behind ChatGPT's Developer mode toggle)
• Everything else — the hub at certfusion.com/mcp-server covers any MCP-compatible client

What's next

Claude and ChatGPT are the first two channels, not the last. The same server already works with any MCP client, and dedicated guides for more assistants are on the way. We're also watching what people actually ask their assistants to do — the prompts you write are the best roadmap for which tools we add next.

If you try it, we'd genuinely love to hear what workflow you automate first: hi@certfusion.com.

Start free at certfusion.com → connect your assistant → and let certificate admin disappear into a chat window.