Let AI agents read and edit live Tiptap documents via MCP
Last updated 22 November 2026. Covers the WhoIsTyping Streamable HTTP MCP server (https://whoistyping.wtf/mcp) and delegated OAuth flow.
Short answer
WhoIsTyping runs a hosted Model Context Protocol (MCP)
server at https://whoistyping.wtf/mcp. Once you approve access in a browser with OAuth (PKCE), AI agents like Claude Code or Codex can create projects, inspect webhook logs, and
read, create, replace or append live collaborative Tiptap documents
in HTML or JSON. Updates flow directly through the Hocuspocus server, so human collaborators see edits appear live without losing their cursors.
Connect Claude Code or Codex
Register the remote MCP server once, then complete the one-time browser approval for your organization:
# Claude Code
claude mcp add --transport http --scope user whoistyping https://whoistyping.wtf/mcp
# Then inside Claude Code: /mcp → whoistyping → Authenticate
# Codex
codex mcp add whoistyping --url https://whoistyping.wtf/mcp
codex mcp login whoistyping
Any MCP client supporting OAuth 2.1 with PKCE S256 and Streamable HTTP can point directly at https://whoistyping.wtf/mcp. Machine-readable instructions live at /mcp.md.
Live document and project tools
| Tool | What it does | Required scope |
|---|---|---|
list_document_content |
Lists documents in a project with size and timestamps. | api.read |
get_document_content |
Reads the live in-memory document (or stored snapshot) as html
or json.
|
api.read |
create_document_content |
Seeds a new collaborative document from HTML or Tiptap JSON. | api.write |
update_document_content |
Replaces or appends (mode: "append") content on the live collaboration server, with optional upsert: true.
|
api.write |
create_project, update_project,
test_webhook
|
Provisions projects, sets webhook URLs and verifies receivers end-to-end. | api.write (+ secrets.read for webhook URLs) |
get_project_secrets |
Reads a project's Document Server ID and secrets when wiring up a Bubble or Tiptap app. | secrets.read |
How live updates preserve collaborator cursors
Unlike overwriting a database text field behind the editor's back,
update_document_content
applies changes inside the running Hocuspocus Yjs document:
-
Replace mode (
mode: "default"): keeps unchanged leading and trailing top-level nodes intact, so collaborators editing elsewhere in the document keep their cursor positions and concurrent edits. -
Append mode (
mode: "append"): inserts new paragraphs, tables or headings at the end of the document without touching earlier content. - Webhook sync stays automatic: every agent write triggers your normal document webhook, so your Bubble or app database stays in sync too.
OAuth scopes, expiry and instant revocation
Agent access is explicitly scoped during browser consent (api.read, api.write, secrets.read, secrets.rotate, api.destroy) and bound to a single organization you own or administer. Refresh tokens expire automatically after 30 days without use (and at most 90 days after approval), and you can revoke any agent immediately under Settings → Agent access.
Using the REST API without an MCP client
For scripts, CI pipelines or custom agent frameworks without MCP support, two options are available:
- Delegated agent OAuth: follow /auth.md for a human-approved device/claim flow against the full OpenAPI v1 spec.
-
Per-project Content API Secret:
call
https://whoistyping.wtf/api/v1/document-servers/{Document Server ID}/documents/{name}directly from your backend without exposing organization-level permissions.
Building a Bubble app with an AI coding agent? Pair this with the Buildprint Bubble rich text editor guide so your agent can install the Bubble plugin and wire up WhoIsTyping in one workflow.