Skip to content
Zeenly

Publish your magazine from Claude

Connect Zeenly to Claude and you can upload, update and publish your magazine by asking for it in plain English. "Upload the November issue and send me the share link." "Swap the PDF for the corrected version." "Which issues are live?"

It works in claude.ai (web, desktop and mobile), Claude Code, and any other app that supports MCP connectors.

What you'll need

  • A Zeenly Pro or Publisher plan (the connector isn't on the free plan), and a brand/publication already set up in your dashboard.
  • Claude on a plan that allows custom connectors. On Team and Enterprise plans, an Owner may need to add the connector for your organisation first.
  • The connector address: https://zeenly.com/mcp

Connect claude.ai (web, desktop or mobile)

  1. In Claude, open Settings → Connectors and choose Add custom connector.
  2. Name it Zeenly and paste https://zeenly.com/mcp as the URL. Leave the advanced settings empty.
  3. Click Add, then Connect. Claude sends you to Zeenly.
  4. Sign in to Zeenly if you aren't already, check the permissions, and click Allow.
  5. Back in Claude, start a new chat and make sure Zeenly is switched on in the chat's tools menu.

The permissions you can give:

  • Read (always on): see your brands, issues, links and reader stats.
  • Edit: upload new issues, replace PDFs, change titles, covers and brand settings.
  • Publish: make issues live, or take them down.

Untick Edit or Publish if you'd rather Claude only looked. You can change your mind by disconnecting and connecting again.

Connect Claude Code

Sign-in works the same way. In a terminal:

claude mcp add --transport http zeenly https://zeenly.com/mcp

Then type /mcp inside Claude Code, pick zeenly and choose Authenticate. Your browser opens the Zeenly consent page.

Prefer a key? Go to Settings → Connectors in Zeenly, create a personal key, and run:

claude mcp add --transport http zeenly https://zeenly.com/mcp --header "Authorization: Bearer YOUR_KEY"

Other MCP apps

Any app that supports remote MCP servers over HTTP can connect to https://zeenly.com/mcp. If it supports OAuth sign-in, use that. If not, create a personal key in Zeenly and send it as an Authorization: Bearer header.

Getting your PDF in

Attach it and ask. Drop the PDF into the chat and say "publish this on Zeenly" (or "upload this as the November issue, don't publish yet"). Claude sends the file to Zeenly itself and comes back with the reader link. Nothing to click.

That needs one setting, once: Claude has to be allowed to run code and reach zeenly.com.

  • In Claude's settings, turn on code execution, and add zeenly.com to the domains it may reach.
  • On a Team or Enterprise plan an Owner may need to allow zeenly.com for the organisation first.

Without that setting, Claude can still read your PDF but can't send the file anywhere, so it falls back to:

  • Upload link. Claude gives you a one-time link. Open it, drop the PDF in, done. It works once and expires after 30 minutes.
  • Public link. If the PDF is already online (your website, Dropbox or Google Drive shared as "anyone with the link"), Claude can import it directly. OneDrive and WeTransfer pages don't work; use an upload link for those.

Automating it

Anything that can run Claude with the Zeenly connector can publish without a person in the loop: Claude Code, scheduled tasks, or your own agent. The PDFs just need to be somewhere Claude can read them.

  • Claude Code: "Upload ~/Magazines/nov-2026.pdf to Zeenly as November 2026 and publish it." Claude creates an upload link and sends the file in one step.
  • A folder or shared drive: "Every month, take the newest PDF in /exports/magazine, upload it as that month's issue, and send me the short link."
  • Files already online: give Claude the address and it imports from there.
  • No sign-in screen available (servers, scripts): create a personal key in Zeenly's Settings → Connectors and connect with it as a Bearer header. Give it only the permissions the job needs.

New issues still arrive unpublished unless the request says to publish, so a scheduled job can upload for you to check first.

Things to try

  • "What's on my Zeenly account? How many issues have I used?"
  • (PDF attached) "Publish this on Zeenly as November 2026."
  • "Upload the November 2026 issue." (no file attached: Claude gives you an upload link)
  • "Import https://example.org/magazine/nov-2026.pdf as November 2026, but don't publish it yet."
  • "Publish November 2026 and give me the short link and embed code."
  • "Replace the PDF of October 2026 with the corrected version."
  • "Rename the October issue to 'October 2026: Conference special'."
  • "How many people read the September issue, and how many clicked the ads?" (paid plans)

What Claude can't do

To keep your account safe, some things stay in the Zeenly dashboard: deleting issues or brands, team members, billing, logos and hotspot links. Claude also can't schedule an issue for a future date yet.

New issues arrive unpublished unless you ask Claude to publish them, so nothing reaches your readers until you say so.

Privacy and security

  • Claude only ever sees the one Zeenly account you approved, and only what you allowed.
  • Zeenly never sees your Claude conversations. It only receives the requests Claude makes, such as "list issues".
  • Every action is logged against your account.
  • See every connected app and key in Settings → Connectors, and disconnect any of them instantly. If you're removed from a team, your connections to that account stop working straight away.
  • Treat personal keys like passwords. If one leaks, disconnect it and create a new one.

Troubleshooting

  • "Couldn't reach the MCP server": check the URL is exactly https://zeenly.com/mcp.
  • Zeenly shows as connected, but Claude says it can't see Zeenly's tools (or you saw "Authorization with Zeenly failed"): in Claude, open Settings → Connectors, disconnect Zeenly and connect it again. Then start a new chat and check Zeenly is switched on in the tools menu.
  • Connected the wrong Zeenly account: on the Zeenly permissions page, choose Use a different Zeenly account before you click Allow. Already connected? Disconnect it in Zeenly's Settings → Connectors, then connect again from Claude.
  • You belong to more than one account: the Zeenly permissions page asks which one to connect. Each connection works on that one account only.
  • Claude says it doesn't have permission: you unticked Edit or Publish. Disconnect in Claude, connect again, and leave them ticked.
  • Upload link says it has expired: ask Claude for a new one. They last 30 minutes and work once.
  • "Available on paid plans": the connector is part of Pro and Publisher. See plans.

Still stuck? Contact support and mention "connector".