Publish documents as links, from inside Claude

Connecting

You need a Celero account. There is no API key to create and nothing to configure — you sign in with the account you already use.

Wherever you add it, leave any header, token or OAuth field empty — Celero uses your sign-in, not a key. Claude then opens the Celero sign-in page; sign in as you normally would and approve access.

On claude.ai — Pro and Max

1. Open Customize › Connectors.
2. Click +, then Add custom connector.
3. Paste the server URL and click Add.

On the Free plan this works too, but you can only have one custom connector at a time.

On claude.ai — Team and Enterprise

An owner or admin adds it once for everyone:

1. Open Organization settings › Connectors and click Add.
2. Hover Custom, then choose Web.
3. Paste the server URL and click Add.

Everyone else then opens Customize › Connectors, finds Celero in the organization's list, and clicks Connect to sign in as themselves.

In Claude Code

Then run /mcp, choose celero, and sign in. Add -s user to the command to make the connector available in every project rather than the current one.

Turning it on in a conversation

Adding the connector does not switch it on everywhere. In a chat, click + at the bottom left, choose Connectors, and enable Celero for that conversation.

Every person who connects authenticates as themselves. Claude sees only the microsites that account can see, and acts only as that account.

What each plan allows

Creating microsites works on any Celero plan. Adding a new version to an existing microsite requires a paid plan — if your account is not eligible, the connector says so in plain language rather than failing.

What Claude can do

Five tools. They are split by whether they change anything, because that decides whether Claude asks you first.

list_microsites

List your microsites. Optionally filtered by name. Returns each one's name, public link, published state and creation date.

get_microsite_conversion_status

Check on a conversion. Large files convert in the background; this reports whether one has finished.

new_microsite_from_url

Turn a document into a microsite. Takes a file at a public https URL — PDF, PowerPoint, Word, Excel, OpenDocument or image — and returns the published link.

update_microsite

Replace a microsite's content. Keeps its URL, so a link you have already shared goes on working and serves the new document. Requires a paid plan.

new_microsite_from_file

Send a file from your machine. Returns a short-lived upload address for a file that is not already on the web, which new_microsite_from_url then uses.

Things you can ask for

• “Turn this PDF into a Celero microsite and give me the link.”
• “Publish the deck at this URL as a microsite called Q3 Board Review.”
• “Upload the PowerPoint on my desktop to Celero and share the link.”
• “List my Celero microsites created this month.”
• “Replace the Q3 Board Review microsite with this updated PDF, keeping the same URL.”

Files and formats

A file can reach Celero two ways: from a public https URL, or straight from your machine.

Supported formats

• PDF
• PPTX
• PPT
• DOCX
• DOC
• XLSX
• XLS
• ODT
• ODP
• ODS
• PNG
• JPEG

Sending a file from your machine

Claude requests a one-time upload address, sends the bytes directly to Celero's storage, then creates the microsite from it. The file never travels through the conversation, and the address only accepts a file of exactly the expected size.

Limits

Anything larger than the direct-upload limit can still be published — put it somewhere with a public https URL and use that instead.

Access and data

For IT administrators reviewing this connector before approving it.

How access works

• Sign-in uses OAuth 2.0 through Celero's identity provider, with PKCE. Each user authenticates individually.
• The connector holds no shared credential and no service account. It can only reach what the signed-in user can reach.
• Access ends when the user disconnects the connector or their Celero access is revoked.

What Claude can see

The microsites in the signed-in user's account — names, links, published state and dates — and the status of conversions that user started. Nothing else in the account is exposed, and the connector reads no other system.

What the connector stores

All of these expire on their own. Document contents are not retained by the connector — files go to Celero's conversion pipeline and the published microsite lives in your Celero account, under the same terms as anything else you upload there.

Data handling is covered by the Celero privacy policy and terms of use.

Troubleshooting

Claude says it needs you to reconnect

Your session expired. Reconnect the connector and sign in again.

The connector will not add, or fails straight away

Check the URL ends in /mcp. The bare hostname has nothing on it and will not connect.

It is connected but Claude does not use it

Connectors are enabled per conversation. Click + at the bottom left of the chat, choose Connectors, and turn Celero on.

Your team cannot see it

On Team and Enterprise, an owner adds the connector once in Organization settings › Connectors. Until then it will not appear in anyone else's list.

A file will not convert

Check the format against the list above, and check the extension is right — Celero chooses how to convert from the file's extension, so a mislabelled file fails. HTML and .zip exports are not supported; export as PDF or PPTX.

A file is too large

Direct uploads stop at 59 MB. Put the file somewhere with a public https URL and ask Claude to publish from there — a PDF has no size limit on that route, because Celero fetches it itself.

Adding a version is refused

Adding a version to an existing microsite requires a paid plan. Creating a new microsite works on any plan.

A conversion seems stuck

Large documents convert in the background. Ask Claude to check the conversion status rather than starting again — a second attempt creates a second microsite.

Support

Questions about the connector, or anything that looks wrong: support@celero.io.

When reporting a problem, it helps to include what you asked Claude to do, the name of the microsite or file involved, and roughly when it happened.