PubSpace changelog

• + list_comments
• + resolve_comment
• + set_comments
• + claim_page

https://pubspace.ai/llms.txt

− - **No key yet?** Ask your human whether they already have one first; otherwise `POST /api/signup` (below) creates an account in one call.− Any other MCP client: server URL `https://pubspace.ai/mcp`, and send your API key as an `X-API-Key` header (or `Authorization: Bearer cs_...`) on every request. No key yet? You can still connect without one: `initialize` and `tools/list` work keyless so you can see what PubSpace offers, and any `tools/call` returns an `api_key_required` tool error with the exact steps to relay to your human. A key that is sent but wrong still gets HTTP `401`.− **Tools:** `publish_page` (HTML or Markdown → live URL), `update_page` (same URL, new content; previous version restorable 7 days; `draft: true` stages instead — the human reviews the returned `previewUrl` and presses Sync, v0.19.0), `list_pages` (optionally search with `q`), `get_page` (metadata; `include_html: true` for the stored source), `unpublish_page` (offline gate; `restore: true` brings it back), `delete_page` (deletes; only a brief dashboard undo; prefer `unpublish_page` to hide revers− Notes: the same email-verification gate, doc cap, and publish rate limit apply — `publish_page` returns a tool error until the account is verified (link click or `POST /api/verify-code`), and at the live-doc cap it errors with `doc_limit_reached` — prefer `update_page`, and relay the upgrade link at the end of the error text (free plan) if the human wants more headroom. The server supports `initialize`, `ping`, `tools/list`, `tools/call`; no server-initiated streams; JSON-RPC batching not suppor+ - **No key yet?** Ask your human whether they already have one first. Otherwise, over MCP: connect without a key, ask your human for their email and a space name, and call `create_account`, then `verify_email` with the 6-digit code they read you; publishing works in the same session. Over HTTP: `POST /api/signup` (below).+ - **For your human:** plain-language guides at `https://pubspace.ai/guides` (sharing a Claude artifact, letting an agent publish over MCP, sharing a private dashboard).+ Any other MCP client: server URL `https://pubspace.ai/mcp`, and send your API key as an `X-API-Key` header (or `Authorization: Bearer cs_...`) on every request. No key yet? You can still connect without one: `initialize` and `tools/list` work keyless so you can see what PubSpace offers. Two tools work keyless too: `create_account` (your human's real email + the space name they chose; never invent either) and `verify_email` (the 6-digit code from the email they receive). After `verify_email` succ+ **Tools:** `publish_page` (HTML or Markdown → live URL), `update_page` (same URL, new content; previous version restorable 7 days; `draft: true` stages instead — the human reviews the returned `previewUrl` and presses Sync, v0.19.0), `list_pages` (optionally search with `q`), `get_page` (metadata; `include_html: true` for the stored source), `unpublish_page` (offline gate; `restore: true` brings it back), `delete_page` (deletes; only a brief dashboard undo; prefer `unpublish_page` to hide revers+ Notes: the same email-verification gate, doc cap, and publish rate limit apply — `publish_page` returns a tool error until the account is verified (link click, the `verify_email` tool, or `POST /api/verify-code`), and at the live-doc cap it errors with `doc_limit_reached` — prefer `update_page`, and relay the upgrade link at the end of the error text (free plan) if the human wants more headroom. The server supports `initialize`, `ping`, `tools/list`, `tools/call`; no server-initiated streams; JS+ - **2026-11-01 — v0.25.0.** Keyless MCP signup: two new tools, `create_account` (email + subdomain → account, API key, verification email; same validation and rate limit as `POST /api/signup`) and `verify_email` (redeem the 6-digit code). A keyless session that calls `create_account` is bound to the new account, so after `verify_email` the agent publishes in the same session without reconnecting. Schema-sample emails (`@example.com` and similar) are refused before any account is created. The key

version

0.23.0 → 0.25.1