Doksi
pro.publifyePublished by publifye.prov1.0.0Updated Oct 24, 2026
Professional PDFs for AI: letters, agreements, agendas, checklists — signatures by link or QR
Overview
Doksi is a hosted MCP server that turns structured content into professional PDFs — letters, agreements, agendas, checklists, covenants — and collects e-signing
- What you can do
- Look up document kinds, purposes, block types and per-kind requirements before composing, and validate a draft without rendering it. Compose structured documents into typeset PDFs and check whether output will be print-ready or a watermarked preview. Issue, share and deliver documents, then rename, list, delete, trash and restore what is kept on the account. Create, describe, fetch, replace, revoke, render and mail signing requests, each with its own link or QR code. Add logos or marks as assets, and check credit balance and access status.
- When to use it
- Useful when an assistant should produce finished, typeset PDFs of known document kinds — personal or official letters, notices, agreements, meeting agendas, checklists, marriage covenants — and route them to signers by link or QR code, rather than laying out arbitrary pages.
- Requirements
- A remote streamable HTTP endpoint; no local package. Sign-in uses OAuth 2.1 with PKCE and open dynamic client registration, so a Publifye account is needed. A free tier gives a small daily allowance; print-ready output needs a plan, a credit or a pass.
Installation
In SourceWeft
- Open Doksi in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/pro.publifye%2Fdoksi/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"doksi": {
"type": "http",
"url": "https://doksi.publifye.com/mcp"
}
}
}README
Doksi — document and PDF MCP server for Claude, Cursor and any MCP client
Doksi turns a structured document into a professional PDF: personal and official letters, notices, agreements, ceremonial covenants, checklists, meeting agendas and schedules — and collects signatures by individual link or QR code. It runs as a hosted MCP server over HTTPS.
Connect
Claude Code: claude mcp add --transport http doksi https://doksi.publifye.com/mcp, then /mcp to
sign in. The discovery chain is the same as for the other servers:
../../docs/connect.md.
Ask what a kind requires before writing it
Most document tools accept a blob and fail at render. Doksi is built the other way round, and four of
its thirty tools exist only so an agent can find out what is expected before it composes
anything: kind_list names the document kinds, purpose_list the purposes, block_types the blocks
a body may contain, and doc_requirements states what one specific kind demands.
That ordering is deliberate. An agent that can ask what a kind requires produces far fewer refusals than one that learns by being refused, and the difference shows up as fewer wasted calls rather than as better error messages.
doc_validate then checks a composed document without rendering it, so a draft can be corrected
while it is still cheap.
Signatures are a request, not a field
Seven tools cover signing, and the shape is a request with its own lifecycle rather than a
boolean on a document: create it, describe it, fetch it, replace it, revoke it, render it, and mail
it. A signer receives an individual link or a QR code; a revoked link stops working; rotating a link
does not invalidate the document it points at. A signing request can be made over a document you
have already kept, by its id, and can be given an expiry.
What you have kept
An issued document is kept on your account. doc_list lists what you have kept, newest first, and
doc_rename gives one a private name that is never printed on it or shown to anyone else.
doc_delete stops its link, every temporary share link and every open signing request over it at
once, and moves it to the trash; doc_trash lists what can still be restored and doc_restore
brings it back within 7 days, with a new link. After that it is purged, and the purge is announced
in advance.
Besides a plan or the daily allowance, a document can be paid for with a purchased credit:
doc_credit_balance shows what is left and when each pack expires, and doc_compose_credit
compiles one PDF against one credit. A refused document is never charged. doc_access_status says
before you compose whether a covenant will come out print-ready or as a watermarked preview.
Marriage covenants: marriage.publifye.com
https://marriage.publifye.com is Doksi's website for marriage covenants. A couple, or their pastor or officiant, tells their own AI assistant what the covenant should say: both names, the date and place, each person's vow, a Bible verse and the witnesses. They choose one of twelve designs and get back a typeset one-page PDF in A4, or A3 for framing, to sign and hang on the wall.
- Twelve designs. Seven painted in watercolour (Champagne Butterfly, Something Blue, Blush Petunias, Bridal Lilies, Garden Roses, Blue Iris, Ivory Magnolia), four drawn (Together in Bloom, Butterfly Garden, Hearts Entwined, Olive & Promise), and Star & Blossom, with a Star of David, made for a Jewish marriage.
- The couple's own words. Each person writes their own vow. The 1662 Book of Common Prayer vows are there as an example of wording. The Bible verse is Ecclesiastes 4:12 unless the couple chooses one to three others, or none.
- English and Norwegian. Sign in ink, or by a personal signing link or QR code.
- A keepsake, not a certificate. Every covenant says at its foot that it is not a civil marriage certificate. A marriage is registered the way the couple's country requires.
- Private. A finished covenant is emailed only to the account that asked for it, and its link is never listed or indexed.
The site has its own marriage-only MCP server, https://marriage.publifye.com/mcp, documented in
services/marriage: nineteen covenant_* tools that hand every covenant to Doksi to
typeset. The Doksi server above makes the same covenant: the assistant calls doc_requirements
with kind: covenant to learn the fields, then doc_compose with content.occasion: marriage.
A covenant can also be made in the browser at https://marriage.publifye.com/create. Designing, checking the wording and a full preview marked PREVIEW are free with
a Publifye account. The print-ready covenant needs a 7-day marriage pass, a Doksi credit or a Doksi
plan; current prices are on https://marriage.publifye.com/store.
What the tools do
Every tool is documented with its exact description, annotations and input schema — 30 in all,
generated from the service's own tools/list, never written by hand.
Machine-readable: tools.json carries all 30 with full JSON Schema, plus every excluded bucket listed by name so the count is auditable.
What it does not do
- Not a word processor. Doksi renders structured documents of known kinds. It is not a place to lay out arbitrary pages.
- Not a legal service. An agreement or covenant rendered here is a document, not advice, and a signature collected here is not a statement about its legal effect in any jurisdiction.
- No silent coercion. A document that does not meet its kind's requirements is refused by
doc_validaterather than rendered with the gaps filled in.
Plans
A free tier includes a small daily allowance. Plans and prices can change; the current ones are always on https://doksi.publifye.com, and where this page and the site differ, the site is right.
Source: services/doksi/README.md at commit 302977c
Tools
0Version history
1- v1.0.0LatestSep 23, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts