SyncPen MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SYNCPEN_API_KEY | Yes | Your SyncPen API key | |
| SYNCPEN_API_URL | No | Optional API URL for development | http://localhost:3000/api/mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| syncpen_searchA | Search SyncPen documents by title and body content (full text). Use this to find documents about a specific topic. |
| syncpen_readA | Read a SyncPen document's content as markdown. Use the document ID from search or list results. |
| syncpen_list_foldersA | List all folders in your SyncPen account. |
| syncpen_list_documentsB | List documents in your SyncPen account, optionally filtered by folder. |
| syncpen_create_folderC | Create a new folder in your SyncPen account. |
| syncpen_rename_folderB | Rename an existing SyncPen folder. |
| syncpen_move_folderA | Move a folder under a new parent folder, or to the root. Rejects circular moves and moves that exceed the nesting depth limit. |
| syncpen_delete_folderA | Delete a folder (moved to trash) along with its subfolders and the documents you own within them. |
| syncpen_createB | Create a new SyncPen document. |
| syncpen_updateB | Update an existing SyncPen document's title and/or content. |
| syncpen_move_documentA | Move a document into a folder, or to the root (un-foldered). |
| syncpen_delete_documentA | Delete a document (moved to trash). Only the document owner can delete it. |
| syncpen_suggest_editA | 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_list_suggestionsA | 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_list_commentsA | Read the comment threads on a document (top-level comments with their replies, line numbers, authors, and resolved state). |
| syncpen_reply_commentA | Reply to a comment thread. The reply is posted under the agent's name and notifies any @mentioned members. |
| syncpen_resolve_commentA | Mark a comment thread as resolved after acting on it. |
| syncpen_publishA | 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_list_connectionsA | 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_recent_changesA | 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 |
| syncpen_relatedA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| SyncPen navigation guide | Token-efficient retrieval discipline and workspace conventions for the SyncPen knowledge base. |
TDQS
Scored across 21 tools
Each tool targets a distinct action on a specific resource (document, folder, comment, suggestion, etc.). Overlap is minimal and well-handled by descriptions, e.g., syncpen_update vs syncpen_suggest_edit are clearly separated by intent.
All tools follow the pattern syncpen_verb_noun in snake_case, consistently using actions like create, delete, list, read, move, etc. This makes it easy for an agent to predict tool names.
21 tools is slightly above the typical range but justified by the server's broad feature set covering documents, folders, comments, suggestions, publishing, search, and analytics. Each tool serves a clear purpose.
The tool surface covers the core document lifecycle (CRUD, search, folders, comments, suggestions, publishing). Minor gaps exist, such as no dedicated tool for retrieving document metadata separately from content, but overall it is well-rounded.