Writespace Mcp

io.github.write-spacePublished by GitHub account write-spacev1.0.0Updated Oct 24, 2026

Persistent docs and memory for AI agents — read, write, organize & search a shared workspace.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & StorageKnowledge & Memory

Overview

AI-generated overview

A hosted MCP server for Writespace, a collaborative markdown docs editor, letting an assistant read, write, organize and search a shared workspace.

What you can do
List workspaces, folders and documents, and fetch a doc as JSON or markdown with its metadata. Run ranked full-text search and query documents by structured metadata. Create, update, upsert, append to, section-replace, move and delete documents. Create, rename and delete folders, including nested ones.
When to use it
Use it when you want an assistant to keep persistent notes, documentation or a searchable knowledge base in a shared workspace that humans edit in the same app. Suited to RAG-style retrieval over team docs and to agents that need to write results back for people to review.
Requirements
A remote HTTP endpoint with bearer authentication. A Writespace account and a personal access token created under Settings, API tokens, sent in the Authorization header. Claude Desktop needs a local bridge such as mcp-remote via npx, so Node.js must be available.
Before you install
The token grants access to your account's workspaces and is shown only once; keep it out of shared configs and revoke it if exposed. Write tools create, modify, move and delete documents and folders, and delete_folder removes its contents. Changes broadcast live to open editors, so collaborators see them immediately. Free tier is limited to 10 documents; paid plans cost money.

Installation

In SourceWeft

  1. Open Writespace Mcp in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.write-space%2Fwritespace-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "writespace": {
      "type": "http",
      "url": "https://app.writespace.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

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)

bash
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:

json
{  "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:    HTTPURL:     https://app.writespace.io/mcpHeader:  Authorization: Bearer ws_pat_YOUR_TOKEN_HERE

Gemini CLI

~/.gemini/settings.json

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.

Source: README.md at commit 1d48fef

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts