dochost
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCHOST_API_KEY | No | API key for headless agents. Create one at dochost.io → Settings → API keys. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| resources | {
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {
"mimeTypes": [
"text/html;profile=mcp-app"
]
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| publishA | Publish Markdown or HTML as a hosted dochost page and get a shareable URL. Respects your plan: link lifetime, password protection, custom slug, and branding all follow your account entitlements. Paid plans publish without dochost branding by default — pass noBranding: false to keep the mark. The link is issued on the account's primary host (a custom domain or subdomain when one is set in Settings › Domains, otherwise dochost.co/d); get_account reports which. |
| list_my_pagesA | List the pages you have published to dochost, newest first. Paginated; returns compact records (no page bodies). |
| get_accountA | Get your plan, page-quota usage, entitlement flags (size cap, custom slug, password, branding), and the primary host new links publish on. Call before publishing so you know your limits up front. The primary host is chosen in the dashboard (manageDomainsUrl), not through this API. |
| get_pageA | Get one of your pages by slug: title, format, status, view/like counts, expiry, and whether it is password-protected. Never returns the page body or the password. |
| update_pageA | Replace the content of one of your pages in place. The URL, view/like counts, and expiry stay the same; only the body, format, and title change. Resending identical content is a no-op. Prefer this over publishing again whenever the user is revising something you already published for them — a second publish creates a second link and strands the one they already shared. |
| delete_pageA | Permanently delete one of your pages by slug. The link stops working immediately and the slug is freed. Deleting an already-deleted page is a safe no-op. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Published link card | Inline card shown after a successful publish: the dochost.co link with a copy button and an open-page link. |
TDQS
Scored across 6 tools
Each tool has a clearly distinct responsibility: publish creates, list_my_pages enumerates, get_page retrieves metadata for one page, update_page modifies content, delete_page removes, and get_account covers account/plan details. The potential publish/update_page overlap is explicitly disambiguated in the descriptions.
Most tools follow a verb_noun pattern: list_my_pages, get_account, get_page, update_page, delete_page. The lone exception is publish, which lacks an explicit object like publish_page, and list_my_pages includes a possessive that the other list/get tools do not.
Six tools is well-scoped for a page hosting service: publish, list, get, update, delete, and account awareness. Each tool covers a necessary workflow step without unnecessary redundancy.
The core page lifecycle is covered: create, list, read metadata, update, delete, plus account/plan information. Minor gaps exist because page bodies are never retrievable via the API, so content recovery or editing an already-published page without the original source is not fully supported.