This guide covers manual MCP server configuration for Context Sync. Use it when auto-config doesn't run or when you need a fully explicit setup.
- You installed locally (auto-config only runs for global installs).
- Your AI client isn't supported by auto-config yet.
- You prefer to maintain MCP configuration in source control (e.g., team onboarding docs).
You can run the server via a global install or via npx. Both work; choose the one that fits your environment.
{
"context-sync": {
"command": "npx",
"args": ["-y", "@context-sync/server"],
"type": "stdio"
}
}{
"context-sync": {
"command": "node",
"args": ["/path/to/@context-sync/server/dist/index.js"],
"type": "stdio"
}
}Notes:
commandmust be on PATH.argsmust include an absolute path when using thenodeoption.- The MCP transport is stdio.
| Field | Description |
|---|---|
command |
Executable to run (usually npx or node). |
args |
CLI arguments for Context Sync. |
type |
MCP transport type. Always "stdio". |
Below are known configuration locations. Each example shows only the MCP section you need to add.
Path
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
Shape
{
"mcpServers": {
"context-sync": {
"command": "npx",
"args": ["-y", "@context-sync/server"],
"type": "stdio"
}
}
}Path
- macOS/Linux:
~/.cursor/mcp.json - Windows:
%USERPROFILE%\.cursor\mcp.json
Shape
{
"mcpServers": {
"context-sync": {
"command": "npx",
"args": ["-y", "@context-sync/server"],
"type": "stdio"
}
}
}Path
- macOS:
~/Library/Application Support/Code/User/mcp.json - Windows:
%APPDATA%\Code\User\mcp.json - Linux:
~/.config/Code/User/mcp.json
Shape
{
"servers": {
"context-sync": {
"command": "npx",
"args": ["-y", "@context-sync/server"],
"type": "stdio"
}
},
"inputs": []
}Path
- Workspace:
./.continue/mcpServers/context-sync.yaml - Global:
~/.continue/config.yaml
Shape
mcpServers:
context-sync:
command: npx
args:
- -y
- @context-sync/server
type: stdioPath
- macOS:
~/Library/Application Support/Zed/settings.json - Windows:
%APPDATA%\Zed\settings.json - Linux:
~/.config/zed/settings.json
Shape
{
"context_servers": {
"context-sync": {
"command": "npx",
"args": ["-y", "@context-sync/server"],
"type": "stdio"
}
}
}Path
- macOS:
~/.codeium/windsurf/mcp_config.json - Windows:
%USERPROFILE%\.codeium\windsurf\mcp_config.json - Linux:
~/.codeium/windsurf/mcp_config.json
Shape
{
"mcpServers": {
"context-sync": {
"command": "npx",
"args": ["-y", "@context-sync/server"],
"type": "stdio"
}
}
}Path
- macOS:
~/Library/Application Support/Code/User/settings.json - Windows:
%APPDATA%\Code\User\settings.json - Linux:
~/.config/Code/User/settings.json
Shape
{
"codeium.mcp": {
"servers": {
"context-sync": {
"command": "npx",
"args": ["-y", "@context-sync/server"],
"type": "stdio"
}
}
}
}Path
- macOS:
~/Library/Application Support/TabNine/config.json - Windows:
%APPDATA%\TabNine\config.json - Linux:
~/.config/TabNine/config.json
Shape
{
"mcp": {
"servers": {
"context-sync": {
"command": "npx",
"args": ["-y", "@context-sync/server"],
"type": "stdio"
}
}
}
}Path
~/.codex/config.toml
Shape
[mcp_servers.context-sync]
command = "npx"
args = ["-y", "@context-sync/server"]Path
~/.claude/mcp_servers.json
Shape
{
"mcpServers": {
"context-sync": {
"command": "npx",
"args": ["-y", "@context-sync/server"],
"type": "stdio"
}
}
}CLI shortcut:
claude mcp add context-sync "npx" -y @context-sync/serverPath
~/.gemini/antigravity/mcp_config.json
Shape
{
"mcpServers": {
"context-sync": {
"command": "npx",
"args": ["-y", "@context-sync/server"],
"type": "stdio"
}
}
}- JSON/TOML/YAML syntax is valid.
- The config file is saved to the correct location.
- You restarted the AI client after editing config.
npxornodeis available in PATH for the user running the AI client.
If things still fail, see docs/TROUBLESHOOTING.md.