Schema | Context Sync MCP

Context Sync MCP

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/1EchA/context-sync-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server