# whoistyping.wtf MCP server

Remote MCP server (Streamable HTTP) for managing one whoistyping.wtf organization:
projects and webhook settings, secrets and the Bubble API token, documents,
document content (Tiptap JSON or HTML) and logs. Tools mirror https://whoistyping.wtf/api/v1.

URL: https://whoistyping.wtf/mcp

## Connect

The client opens a browser once. Sign in as an owner or admin, choose the
organization and approve. The client then renews its own access with refresh
tokens: it lasts until 30 days without use, at most 90 days after approval.
Revoke it anytime in Settings → Agent access.

Claude Code:

    claude mcp add --transport http --scope user whoistyping https://whoistyping.wtf/mcp

Then run /mcp in Claude Code and choose whoistyping → Authenticate.

Codex:

    codex mcp add whoistyping --url https://whoistyping.wtf/mcp
    codex mcp login whoistyping

On a machine without a browser: codex mcp login whoistyping --no-browser,
open the printed URL anywhere, approve, and paste the final localhost URL back.

T3 Code: add the server to the provider T3 runs (the Claude Code or Codex
command above, user scope); new T3 threads on that provider see its tools.

Other clients: point any MCP client that supports OAuth at https://whoistyping.wtf/mcp.

## Protocol

- Protocol versions: 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26 (2026-07-28 stateless; earlier via initialize). No sessions, no server-initiated streams: GET returns 405.
- Authorization (MCP spec): protected-resource metadata at https://whoistyping.wtf/.well-known/oauth-protected-resource/mcp; authorization server metadata at https://whoistyping.wtf/.well-known/oauth-authorization-server.
- Authorization code + PKCE (S256) at https://whoistyping.wtf/oauth2/authorize; Client ID Metadata Documents or Dynamic Client Registration at https://whoistyping.wtf/oauth2/register (public clients, no secret); redirect URIs must be HTTPS or localhost.
- Send resource=https://whoistyping.wtf/mcp on authorization and token requests. Access tokens are bound to it and last one hour; refresh tokens rotate on every use, and reusing a spent one revokes the connection.
- Scopes: api.read, api.write, secrets.read, secrets.rotate, api.destroy; see https://whoistyping.wtf/auth.md. A tool call without the scope it needs gets HTTP 403 with WWW-Authenticate error="insufficient_scope" and the missing scopes.
- Agents without an MCP OAuth client can use the auth.md flow (https://whoistyping.wtf/auth.md) with resource=https://whoistyping.wtf/mcp on the token request.
