ilolink

ilolink lets people publish Markdown, HTML, PDFs, DOCX files, and other document types as shareable links that anyone can open without signing in. It also shows read analytics such as views, read-through, heatmaps, comments, and reactions, and includes an MCP connector for team AI assistants.

AI Помощник Файлов AI Ассистент Документов AI Аналитика Ассистент

Посетить Сайт

Publish documents as links, and track how they were read

ilolink turns a document, file, or AI-generated page into a shareable link that readers can open without creating an account. It supports Markdown, HTML, PDF, DOCX, JSON, CSV, diagrams, and images, with the option to publish publicly, unlisted, password-protected, or on an expiry date.

Alongside publishing, ilolink provides reading analytics such as views, unique readers, read-through percentages, heatmaps, comments, and reactions. It also includes an MCP connector and team registry so assistants can publish documents and share team knowledge through the same workspace.

Core capabilities

Publish many document formats

Share Markdown, HTML, PDF, DOCX, JSON, CSV, diagrams, and images as a single link. The site also says content can be pasted or uploaded, and documents are auto-detected without choosing a format first.

Reader access without sign-in

Anyone with the link can open a published document without creating an account. Publishing needs an account, but reading does not.

Reading analytics and feedback

Track views, unique readers, read-through, heatmaps, referrers, countries, devices, comments, and reactions. Analytics are presented both on the page and in a private dashboard view.

In-place revision with version history

Update a document without changing its link. The previous version is kept, which helps avoid breaking shared references or sending readers to the wrong file.

Team registry for shared AI guidance

Store team artifacts such as skills, agents, specs, design docs, plans, workflows, handoffs, decisions, runbooks, and evals in one shared registry that teammates’ assistants can fetch by name.

MCP connector for assistants

Connect ilolink to Claude, Claude Code, ChatGPT, or another MCP-compatible assistant so it can publish documents, search published pages, and read or write team registry entries from chat.

Where ilolink fits

Sharing a draft as a clean link
Use ilolink when you want to send a proposal, spec, report, or handoff as a link rather than as an attachment. Readers can open it without logging in, and you can revise the page in place if the content changes.
Reviewing how a document was read
Use the analytics when you need to know whether people opened a page, how far they got, and where they stopped. Heatmaps and comments make it easier to see which sections drew attention or confusion.
Keeping team agent instructions in one place
Store recurring guidance such as commit style, runbooks, or specs in the registry so assistants across the team read the same reviewed version. This is useful when you want consistent behavior across repos and sessions.
Publishing from an AI assistant
If your workflow starts in Claude, Claude Code, or ChatGPT, the MCP connector lets the assistant publish content as a live page and return the link, reducing copy-paste between the chat and the publishing surface.
Handoffs and session continuity
Teams can use session transfers and other registry artifacts to preserve what was decided, what is still open, and what the next person should pick up. That is useful for long projects and shared operational work.

Pros and Cons

Pros

Readers do not need an account to open shared documents.
Team plans are one-time payments rather than recurring subscriptions.
Supports both outward-facing document sharing and internal team knowledge sharing.
Provides concrete read analytics, including read-through and heatmaps, not just simple view counts.
Connects to MCP-compatible assistants and works with Claude, Claude Code, and ChatGPT.

Cons

Publishing requires an account.
Published documents are limited to 15 MB each.
PDFs open in the browser’s built-in viewer, so read-depth and heatmaps do not work inside the PDF itself.
Some team-registry behavior is controlled by team settings, such as requiring review before member writes go live.

FAQ

Do readers need an account to open a published document?

No. Anyone with the link can open a published document without signing in. Accounts are for people who publish and, in teamspaces, for invited teammates.

What kinds of files can I publish?

The site says ilolink can publish Markdown, HTML, PDF, DOCX, JSON, CSV, diagrams, and images. It also supports pasting content directly or uploading a file.

Can I update a document without changing its link?

Yes. ilolink supports revising a document in place so the URL stays the same while the previous version remains available.

How does the team registry work with AI assistants?

Teams can store shared artifacts such as skills, specs, plans, handoffs, runbooks, and other guidance in a registry that assistants can read and write through MCP. Some teams can require admin review before a member’s write becomes active.

Are there file size or expiry limits?

The site states that each published document can be up to 15 MB. It also offers expiring links, but the exact expiry rules are not detailed in the provided source text.

Quick Facts

Category: Document publishing and AI workflow tool
Primary use: Publish shareable documents and track readership
Audience: Individuals, teams, and AI-assisted workflows
Access model: Publishing requires an account; reading does not
Connectivity: MCP connector for Claude, Claude Code, ChatGPT, and other MCP-compatible assistants
Pricing model: Free for one person; team plans are one-time payments