mcpField
W
writespace-mcp

writespace-mcp

Remote
github.com/write-spaceProductivity0Updated 18w ago
Repository

About writespace-mcp

writespace-mcp is a hosted document workspace and MCP server for agents and people collaborating on persistent docs. It combines markdown editing with searchable content, structured metadata, and live updates to open editors.

Key features

  1. 01Read and search workspace documents
  2. 02Create and edit Markdown or Tiptap content
  3. 03Organize folders and documents
  4. 04Query documents by metadata
  5. 05Notify open editors of agent changes

Use cases

  1. 01Keep persistent agent notes in shared docs
  2. 02Search workspace content for retrieval
  3. 03Make targeted edits to a document section

MCP support

Exposes workspace reading, search, writing, and organization as MCP tools over hosted HTTP. Clients authenticate with a Bearer token.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://app.writespace.io/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://app.writespace.io/mcpAuth required

Tools

Details

From the project README

Writespace MCP Server

A remote, hosted Model Context Protocol server for Writespace — a real-time collaborative document editor. Give Claude, ChatGPT, Gemini, Cursor, or any MCP-speaking agent a shared docs workspace it can read, write, organise and search alongside you.

Endpoint: https://app.writespace.io/mcp (HTTP transport, Bearer auth) Free tier: yes — up to 10 documents, no card required → sign up

What it does

Writespace is a markdown-first doc editor for humans with an MCP server built in for agents. Every action you can take in the app is exposed as a tool your model can call:

  • Read — walk the workspace tree, fetch any doc as lossless JSON or markdown, run ranked full-text search (drop it straight into your agent as RAG retrieval)
  • Write — create docs, append content, replace a single section by its heading, shallow-merge structured metadata
  • Organise — create/rename/move folders, move docs, query docs by metadata ({ status: "accepted" })

Agent writes broadcast over Realtime, so open editors reload live. Humans and agents work on the same canvas — no export step, no format negotiation.

Quick start

Three steps, two minutes:

  1. Get a token — sign in at app.writespace.io, open Settings → API tokens, create a token (shown once, revocable any time).
  2. Endpoint — one hosted endpoint for all accounts: https://app.writespace.io/mcp
  3. Configure your client — snippets below.
Claude Code (CLI)
claude mcp add --transport http writespace \
  https://app.writespace.io/mcp \
  --header "Authorization: Bearer ws_pat_YOUR_TOKEN_HERE"
Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json

Claude Desktop's config supports only local (stdio) servers, so a remote HTTP server is bridged through mcp-remote, which Claude Desktop launches locally and which forwards to the endpoint:

{
  "mcpServers": {
    "writespace": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://app.writespace.io/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer ws_pat_YOUR_TOKEN_HERE"
      }
    }
  }
}

Notes:

  • The token goes in the AUTH_HEADER env var (and --header Authorization:${AUTH_HEADER} with no space after the colon) because mcp-remote mishandles spaces in --header arguments.
  • Claude Desktop launches with a minimal PATH. If npx isn't found, use its absolute path (e.g. /usr/local/bin/npx, or your nvm path) — and add a matching "PATH" entry to env if it relies on a versioned node.
  • Fully quit and reopen Claude Desktop (Cmd-Q) after editing — the config is read only at launch.
Cursor

Settings → MCP → Add server

Type:    HTTP
URL:     https://app.writespace.io/mcp
Header:  Authorization: Bearer ws_pat_YOUR_TOKEN_HERE
Gemini CLI

~/.gemini/settings.json

{
  "mcpServers": {
    "writespace": {
      "httpUrl": "https://app.writespace.io/mcp",
      "headers": {
        "Authorization": "Bearer ws_pat_YOUR_TOKEN_HERE"
      }
    }
  }
}

Any other spec-compliant MCP client works the same way: HTTP transport + Authorization: Bearer header.

Tools

Every tool except list_workspaces takes a workspace_id — call list_workspaces first to discover them.

ToolDescription
list_workspacesList every workspace you belong to
list_foldersList folders, optionally nested under a parent
list_docsList documents, optionally scoped to a folder; returns metadata per row
get_docFetch a doc by ID — canonical Tiptap JSON + markdown rendering + metadata
searchRanked full-text search with <<match>> snippets
query_docsFind docs whose metadata contains a JSON object (Postgres JSONB @>)
create_docCreate a doc from Tiptap JSON or markdown
update_docUpdate title, content, or metadata (shallow-merge; null deletes a key)
upsert_docCreate-or-update by title within an optional folder — idempotent
append_to_docAppend markdown / Tiptap JSON to an existing doc
replace_sectionReplace a section's body by its heading text — surgical edits
delete_docDelete a doc by ID
move_docMove a doc to another folder (folder_id: null → root)
create_folderCreate a folder, optionally nested
rename_folderRename a folder — IDs stay stable, links don't break
delete_folderDelete a folder and its contents

Full reference with format notes and troubleshooting: writespace.io/connect

Design notes

  • Lossless content, two formats — reads return both content (Tiptap JSON) and content_markdown; writes accept either. Markdown round-trips for everything the editor supports, including tables, task lists, and mermaid diagrams.
  • Lean write responses — write tools return only metadata by default, saving 80–95% of the payload on long docs. Pass include_content: true to echo the body.
  • Structured metadata — every doc carries a JSONB metadata field. Treat it as queryable frontmatter: write it, shallow-merge it, query by containment.
  • Stable cross-doc links — reference docs as writespace://doc/<id>; IDs survive renames and moves.
  • Live reload — MCP writes notify open editors over Realtime; they refetch in the same tab.

Use cases

Auth & security

  • Per-agent personal access tokens, issued and revoked from Settings — scoped to your account, easy to rotate
  • Tokens are shown once at creation
  • Standard Authorization: Bearer ws_pat_… header; spec-compliant HTTP transport

Links


© 2026 Writespace · Pro is $5/user/month, free tier available.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.