Docs · Connect your AI
Connect your AI in under five minutes.
Syncpen ships a first-class MCP server — run it locally, or connect to our hosted URL. Point Claude Code, Claude Desktop, Cursor, Cline, or Windsurf at your workspace, and your AI can read, search, draft, and suggest edits you approve. One API key, the same workspace everywhere.
Step 1
Get your API key
In Syncpen, open Settings → API Keys → Enable API Access → Create Key. Copy it — the key is shown once and looks like sp_…. Every connection method below uses this key.
Step 2
Add Syncpen to your client
Two ways: a single command for Claude Code, or the universal mcpServers block that every other MCP client uses — the block is identical everywhere, only the config file location changes (see below).
$ claude mcp add syncpen \
--env SYNCPEN_API_KEY=sp_your_key_here \
-- npx -y syncpen-mcp{
"mcpServers": {
"syncpen": {
"command": "npx",
"args": ["-y", "syncpen-mcp"],
"env": {
"SYNCPEN_API_KEY": "sp_your_key_here"
}
}
}
}Every major client
Same block — pick where it goes.
Claude Code
claude mcp add (CLI)
One command — the terminal form shown above. Then run /mcp to verify.
Claude Desktop
claude_desktop_config.json
Settings → Developer → Edit Config, paste the block, restart the app.
Cursor
~/.cursor/mcp.json
Or Settings → MCP → Add new server. Project-level .cursor/mcp.json also works.
Cline (VS Code)
cline_mcp_settings.json
MCP Servers → Configure MCP Servers, paste the block.
Windsurf
~/.codeium/windsurf/mcp_config.json
Cascade → MCP settings → add server, then refresh.
Any MCP client
.mcp.json
Drop the mcpServers block into your client's MCP config. Stdio, Node via npx.
Cloud & browser clients
Or connect over a hosted URL — no local install.
Two ways to connect remotely. Clients with a token field — Cursor, Claude Code's HTTP transport, or any client via the mcp-remote bridge — use the URL with your API key as a header (below). Clients with a one-click connector — claude.ai, Claude Desktop, and Cowork — use OAuth: Add custom connector → paste the URL → sign in → Allow. No key to copy; access is granted on consent, and your scopes still apply.
MCP server URL
https://www.syncpen.io/api/mcp-server/mcp{
"mcpServers": {
"syncpen": {
"url": "https://www.syncpen.io/api/mcp-server/mcp",
"headers": {
"Authorization": "Bearer sp_your_key_here"
}
}
}
}Header auth uses the same sp_… key, sent as Authorization: Bearer sp_…. OAuth connector clients sign in instead — no key to paste. Either way a read-only grant can read but not write or publish: the same least-privilege scopes apply to both paths.
Step 3
Verify, then put it to work
Run /mcp in Claude Code (or restart your client). You should see “syncpen” connected with its tools listed. Then try a prompt:
› Search my Syncpen notes for the Q3 review and draft a summary document.
› Read this doc, then suggest tighter edits — I'll accept or reject each one.
› Reply to the open comments in this document and resolve the ones you've answered.
What your AI can do
Every tool the Syncpen MCP server exposes.
Read & search
read · search · list_documents · list_folders · list_connections
Write
create · update
Suggest — track-changes
suggest_edit · list_suggestions
Comments
list_comments · reply_comment · resolve_comment
Organize
create / rename / move / delete folder · move / delete document
Publish
publish → WordPress · Ghost · Sanity
Good to know
The API key is required.
The bare claude mcp add … -- npx -y syncpen-mcp form (no SYNCPEN_API_KEY) connects unauthenticated, and every tool call fails. Always include the key.
Two ways to connect: local or hosted.
The npx setup runs locally, so Node must be installed and the client must be able to run a local server — ideal for Claude Code and Claude Desktop. Cloud and browser-only clients can't run a local server, so point them at the hosted URL above instead. After editing a config file, fully restart the client so it reloads MCP servers.
Ready to connect?
Create your free account, grab an API key, and point your AI at your workspace.