dochost-mcp

Get my dochost account

get_account

Read-only

Get your plan, page-quota usage, entitlement flags (size cap, custom slug, password, branding, subdomain, custom domain), and the primary host new links publish on. Call when you need plan limits, domain details or paid-option availability; a basic publish can use defaults without this extra call. The primary host is chosen in the dashboard (manageDomainsUrl), not through this API.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`plan`	Yes
`password`	No
`analytics`	No
`pageQuota`	No
`pagesUsed`	No
`sizeCapMb`	No
`customSlug`	No
`noBranding`	No
`primaryHost`	No	Host new links publish on: a custom domain, `{sub}.dochost.co`, or `dochost.co/d`.
`customDomain`	No	Whether this plan may point a hostname the user owns at their pages (set it at manageDomainsUrl).
`pagesRemaining`	No
`permanentLinks`	No
`customSubdomain`	No	Whether this plan may claim a {name}.dochost.co subdomain (set it at manageDomainsUrl).
`manageDomainsUrl`	No	Dashboard page where the user adds domains and picks the primary one. Send them here to change it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 20, 2026

addedOutput schema / properties / customDomain

Added value: +{
+  "description": "Whether this plan may point a hostname the user owns at their pages (set it at manageDomainsUrl).",
+  "type": "boolean"
+}

addedOutput schema / properties / customSubdomain

Added value: +{
+  "description": "Whether this plan may claim a {name}.dochost.co subdomain (set it at manageDomainsUrl).",
+  "type": "boolean"
+}

Changed2 schema fields changedSep 6, 2026

addedOutput schema / properties / manageDomainsUrl

Added value: +{
+  "description": "Dashboard page where the user adds domains and picks the primary one. Send them here to change it.",
+  "type": "string"
+}

addedOutput schema / properties / primaryHost

Added value: +{
+  "description": "Host new links publish on: a custom domain, `{sub}.dochost.co`, or `dochost.co/d`.",
+  "type": "string"
+}

Changed1 schema field changedJun 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "analytics": {
+      "enum": [
+        "none",
+        "totals",
+        "full"
+      ],
+      "type": "string"
+    },
+    "customSlug": {
+      "type": "boolean"
+    },
+    "noBranding": {
+      "type": "boolean"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "pageQuota": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "pagesRemaining": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "pagesUsed": {
+      "type": "integer"
+    },
+    "password": {
+      "type": "boolean"
+    },
+    "permanentLinks": {
+      "type": "boolean"
+    },
+    "plan": {
+      "enum": [
+        "free",
+        "pro",
+        "max"
+      ],
+      "type": "string"
+    },
+    "sizeCapMb": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "ok",
+    "plan"
+  ],
+  "type": "object"
+}

First observedJun 18, 2026

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish this as a read-only, non-destructive, closed-world operation, so the bar is lower. The description still adds real value by disclosing the returned entitlement categories and the important constraint that the primary host is configured in the dashboard, not through this API.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the return contents and followed by usage guidance and one caveat. The entitlement list is long but each item is informative, and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although an output schema exists and the description need not explain return values, it covers purpose, when/when-not to call, and a behavioral constraint. Nothing an agent needs in order to decide whether to invoke this parameterless read is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema-based baseline of 4 applies. The description correctly implies no input is needed, describing only the information returned rather than any arguments.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource and then enumerates exactly what is retrieved: plan, page-quota usage, entitlement flags, and the primary publish host. That level of detail clearly separates it from siblings like get_page, get_page_content, and publish.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states both when to call (need plan limits, domain details, paid-option availability) and when not to (a basic publish can use defaults without this extra call). It also flags that the primary host is set in the dashboard rather than via the API, removing a likely mis-invocation path.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All dochost-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.