Context Sync MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| write_contextA | Batch write memory entries to .context/ files. Supports append (for gotchas, architecture, api_notes) and overwrite (for progress, summary). Use this to record discoveries, decisions, and progress during development. |
| sync_initA | Bootstrap Context Sync for a project that has not been initialized yet. Use for first-time setup requests such as /sync-init, 'init context', 'initialize sync', or 'set up context sync for this repo'. If context already exists, do not overwrite it; guide the user to /sync-load instead. |
| sync_pushA | Push local .context/ files to remote git. Auto-generates SUMMARY.md. Use only for save/upload/push requests such as /sync-save, 'sync push', 'save context', or 'upload context'. Do NOT use this tool for pull/load/restore/new-device recovery requests. |
| sync_loadA | Pull latest .context/ files from remote git and return their contents. Use for load/pull/restore/recover requests such as /sync-load, 'sync pull', 'pull context', 'load context', or 'restore context on a new device'. Do NOT use sync_push for these requests. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The four tools split cleanly by lifecycle stage: local writing, initialization, git push, and git pull. Each description includes clear usage triggers and negative constraints, so an agent should not confuse them.
Three tools follow a sync_<verb> pattern, while write_context uses verb_<object>. The snake_case convention is consistent and the actions are clear, so this is only a minor structural deviation.
Four tools is well-scoped for a context sync server. Each tool earns its place by covering a necessary step: initialize, write, push, and load.
The core lifecycle from initialization to local writes to remote sync is covered, including first-time setup and new-device recovery. Minor gaps like delete operations or sync status checks are missing but are not blocking for the main workflow.