syncpen_create
Create a new SyncPen document. If a semantically similar document already exists, the response flags it — consider updating that one instead of creating a near-duplicate.
LABSCO SUMMARY
An agent can write here, or ask to — and that is a different tool, not a setting.
syncpen_update writes; syncpen_suggest_edit leaves a pending suggestion a person accepts or rejects in the editor, anchored on offsets or on a snippet so it lands in the right place. A document owner can force the second path, and both the update and delete tools report how many other documents link to the one you touched — the detail that keeps a maintained knowledge base from quietly filling with broken links. Two more habits worth forming: create tells you when a semantically similar document already exists, and recent_changes with a since parameter shows human and agent edits in the same feed.
What it is
A writing workspace an agent can work inside rather than alongside. It searches, reads, drafts, organises and publishes in the same documents a human is editing, and it can propose an edit as a pending suggestion instead of writing it — the document does not change until someone accepts. Publishing targets WordPress, Ghost and Sanity.
What you get
- syncpen_search runs keyword search over titles and content, or semantic search that finds documents by meaning even when they share no words with the query; syncpen_read returns one as markdown
- syncpen_create flags a semantically similar existing document in its response, so a near-duplicate becomes a decision rather than an accident
- syncpen_update reports how many other documents link to the one you changed, and syncpen_delete_document does the same before you leave dangling links behind
- syncpen_suggest_edit proposes a change anchored either on character offsets or on a unique snippet and leaves the document untouched until a human accepts it in the editor; syncpen_list_suggestions shows what is still pending
- An owner can mark a document suggest-only or excluded, and a direct write or an agent deletion is then refused outright
- Comment threads are readable and answerable: syncpen_list_comments with replies, line numbers, authors and resolved state, syncpen_reply_comment posting under the agent's name and notifying @mentions, and syncpen_resolve_comment
- Folders can be created, renamed, moved — circular moves and over-deep nesting are rejected — and deleted, which trashes subfolders and the documents you own inside them
- syncpen_recent_changes is a time-ordered feed of who created, edited or trashed what, covering in-app human edits and agent writes alike, with a since parameter for catching up
- syncpen_related suggests what to read next by blending co-access from the change history with the explicit editor links in the markdown, in both directions
- syncpen_publish ships a document to a connected WordPress, Ghost or Sanity target, auto-selecting when only one is active, with syncpen_list_connections to find the connectionId when several are
Requirements
Runs over stdio as npx -y syncpen-mcp with SYNCPEN_API_KEY, an sp_ key created under Settings → API Keys once API access is enabled — it is shown only once. SYNCPEN_API_URL only needs setting to target a local instance. MIT.
Setup effort
One command plus a key — npx -y syncpen-mcp, then supply credentials
USE CASES
01
Finding what you already wrote about something
Semantic search finds the document by meaning even when it uses none of your words, then reads back as markdown you can work with.
02
Letting an agent improve a document without it changing under you
The proposal lands as a pending suggestion anchored to a specific snippet, and the document stays as it was until someone accepts it in the editor.
03
Adding to a knowledge base without duplicating it
Create flags a semantically similar document if one exists, so the choice between a new note and an update is made before the duplicate lands.
04
Answering the comments left on a draft
Read the threads with their line numbers and authors, reply under the agent's name so @mentions get notified, and resolve the ones that are dealt with.
05
Shipping a finished piece to your site
Find the right connection when there is more than one, then publish to WordPress, Ghost or Sanity in a single call.
06
Catching up on a shared workspace
A time-ordered feed of what changed since you last looked, covering both people and agents, with a suggestion of what to read next from a document you are already in.
21 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
syncpen_create_folder
Create a new folder in your SyncPen account.
syncpen_delete_document
Delete a document (moved to trash). Only the document owner can delete it. Suggest-only/excluded documents refuse agent deletion. The response reports how many other documents linked to this one, so you can fix any now-dangling links.
syncpen_delete_folder
Delete a folder (moved to trash) along with its subfolders and the documents you own within them.
syncpen_list_comments
Read the comment threads on a document (top-level comments with their replies, line numbers, authors, and resolved state).
syncpen_list_connections
List your connected CMS targets (WordPress, Ghost, Sanity) and their connectionIds. Use before syncpen_publish to find the connectionId when a target has more than one active connection.
syncpen_list_documents
List documents in your SyncPen account, optionally filtered by folder.
syncpen_list_folders
List all folders in your SyncPen account.
syncpen_list_suggestions
List a document's suggestions so you can see what is still pending. Defaults to pending only; pass status 'all' to include accepted/rejected.
syncpen_move_document
Move a document into a folder, or to the root (un-foldered).
syncpen_move_folder
Move a folder under a new parent folder, or to the root. Rejects circular moves and moves that exceed the nesting depth limit.
syncpen_publish
Publish a SyncPen document to a connected CMS (WordPress, Ghost, or Sanity). Auto-selects the connection when only one is active for the target; otherwise pass connectionId.
syncpen_read
Read a SyncPen document's content as markdown. Use the document ID from search or list results.
syncpen_recent_changes
A time-ordered feed of recent workspace changes — who created, edited, or trashed which documents, and when. Surfaces both in-app human edits and agent/API writes. Use it to catch up on what changed since you last looked (pass since), or to scope to one folder.
syncpen_related
Given a document, suggest what else to look at — a learned 'what to read next' signal. Blends co-access (documents you worked on in the same sessions as this one, from the change history) with the explicit /editor links in the markdown (both directions). Returns documents ranked by relevance, each with a plain-language reason. Use it to warm-start on a topic or find the documents that tend to travel together.
syncpen_rename_folder
Rename an existing SyncPen folder.
syncpen_reply_comment
Reply to a comment thread. The reply is posted under the agent's name and notifies any @mentioned members.
syncpen_resolve_comment
Mark a comment thread as resolved after acting on it.
syncpen_search
Search SyncPen documents. Modes: 'all' (default), 'title', 'content' are keyword/full-text; 'semantic' finds documents by meaning (embeddings) even when they share no words with the query. Use this to find documents about a specific topic.
syncpen_suggest_edit
Propose an edit to a document as a pending suggestion that a human accepts or rejects in the editor. The document is NOT changed until accepted. Use this instead of syncpen_update when you want human approval. Anchor the edit either by character offsets {from,to} or by a unique snippet {text} to replace.
syncpen_update
Update an existing SyncPen document's title and/or content. Documents whose owner set them to suggest-only or excluded will refuse a direct write — use syncpen_suggest_edit there instead. The response reports how many other documents link to this one, so you can check they still make sense after your change.
BEFORE YOU INSTALL
What to know first
Tools you get
21 tools when we connected; the project documents 29. The eight extra tools act on Drive, Slack, Notion or World News and appear once those integrations are connected in your Syncpen workspace.
Requires
- npx on PATH
- SYNCPEN_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y syncpen-mcpMCP Clients
Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"syncpen": {
"command": "npx",
"args": [
"-y",
"syncpen-mcp"
],
"env": {
"SYNCPEN_API_KEY": "<YOUR_SYNCPEN_API_KEY>"
}
}
}
}
