Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
Persistent docs and memory for AI agents — read, write, organize & search a shared workspace.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
在终端中运行这条命令
claude mcp add --transport http writespace https://app.writespace.io/mcp --header 'Authorization: your-value'运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"writespace": {
"url": "https://app.writespace.io/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"writespace": {
"type": "http",
"url": "https://app.writespace.io/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
Authorization 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 write-space 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于5个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Context7, Codebase Memory, Exa
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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
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:
{ 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.
Three steps, two minutes:
https://app.writespace.io/mcpclaude mcp add --transport http writespace \
https://app.writespace.io/mcp \ --header "Authorization: Bearer ws_pat_YOUR_TOKEN_HERE"
~/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:
AUTH_HEADER env var (and --header Authorization:${AUTH_HEADER} with no space after the colon) because mcp-remote mishandles spaces in --header arguments.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.Settings → MCP → Add server
Type: HTTP
URL: https://app.writespace.io/mcp Header: Authorization: Bearer ws_pat_YOUR_TOKEN_HERE
~/.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.
Every tool except list_workspaces takes a workspace_id — call list_workspaces first to discover them.
| Tool | Description |
|---|---|
list_workspaces | List every workspace you belong to |
list_folders | List folders, optionally nested under a parent |
list_docs | List documents, optionally scoped to a folder; returns metadata per row |
get_doc | Fetch a doc by ID — canonical Tiptap JSON + markdown rendering + metadata |
search | Ranked full-text search with < > snippets |
query_docs | Find docs whose metadata contains a JSON object (Postgres JSONB @>) |
create_doc | Create a doc from Tiptap JSON or markdown |
update_doc | Update title, content, or metadata (shallow-merge; null deletes a key) |
upsert_doc | Create-or-update by title within an optional folder — idempotent |
append_to_doc | Append markdown / Tiptap JSON to an existing doc |
replace_section | Replace a section's body by its heading text — surgical edits |
delete_doc | Delete a doc by ID |
move_doc | Move a doc to another folder (folder_id: null → root) |
create_folder | Create a folder, optionally nested |
rename_folder | Rename a folder — IDs stay stable, links don't break |
delete_folder | Delete a folder and its contents |
Full reference with format notes and troubleshooting: writespace.io/connect
content (Tiptap JSON) and content_markdown; writes accept either. Markdown round-trips for everything the editor supports, including tables, task lists, and mermaid diagrams.include_content: true to echo the body.metadata field. Treat it as queryable frontmatter: write it, shallow-merge it, query by containment.writespace://doc/ ; IDs survive renames and moves.Authorization: Bearer ws_pat_… header; spec-compliant HTTP transport© 2026 Writespace · Pro is $5/user/month, free tier available.