Labsco
MCP SERVER

Syncpen

by airbuzz

An agent that works inside the same live documents you edit — proposing changes as suggestions you accept, or publishing straight to your CMS.

Team Wikis & Documentation PlatformsVerified
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