devsync-mcp
Allows management of EditorConfig files for consistent coding styles across the team.
Allows management of Git configuration files (e.g., .gitconfig, .gitignore_global), merging team-standard Git settings with personal customizations.
Allows management of Zsh shell configuration (e.g., .zshrc), merging team shell aliases and PATH additions with personal settings.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@devsync-mcpsync the team's dev configs to my machine"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
devsync-mcp
MCP server for AI-merge of team dev configurations. Works with any MCP-capable IDE (Claude Code, Cursor, Windsurf, Copilot, Zed, etc.).
What it does
Teams maintain a shared config profile repo (shell configs, git settings, AI rules, editor configs). devsync-mcp provides MCP tools that let the IDE's LLM intelligently merge team configs with your personal configs — preserving your customizations while incorporating team standards.
Key insight: The MCP server does NOT call an LLM. It provides source and target content to the host IDE's LLM, which performs the intelligent merge.
Related MCP server: Logica Context
Install
pip install devsync-mcpMCP Configuration
Add to your IDE's MCP settings:
{
"mcpServers": {
"devsync-mcp": {
"command": "devsync-mcp",
"transport": "stdio"
}
}
}Tools
Tool | Purpose |
| Clone/pull team config repo |
| List configs in a profile |
| Scan environment for existing configs |
| Return source + target for LLM merge |
| Write merged content with backup |
| Pull latest + present merge plan |
| List previous merge backups |
| Restore from backup |
| Show merged/pending/changed status |
AI-Merge Flow
1. pull_team_profile(git_url) → downloads team config repo
2. list_profile_configs(profile) → shows available configs
3. detect_current_configs() → finds your existing configs
4. preview_merge(profile, config) → returns {source_content, target_content}
5. HOST LLM reads both, produces intelligent merge
6. apply_merge(target, merged) → writes with backupTeam Profile Format
Create a devsync-profile.yaml in your team config repo:
name: acme-team-config
description: ACME Corp standard dev environment
version: 1.0.0
configs:
- name: zshrc-additions
file: shell/zshrc-additions.sh
target: ~/.zshrc
type: shell_profile
description: Team shell aliases and PATH additions
- name: claude-rules
file: ai-rules/claude-rules.md
target: CLAUDE.md
type: ai_rules
description: Team coding standards for Claude CodeConfig Types
shell_profile—.zshrc,.bashrc,.bash_profile,.profilegit_config—.gitconfig,.gitignore_globaleditor_config—.editorconfigai_rules—CLAUDE.md,.cursorrules,AGENTS.md, etc.vscode_settings—.vscode/settings.json, etc.ssh_config—.ssh/configcustom— any file with explicit source/target mapping
Claude Code Skill
Install the /sync-team skill for a guided experience:
cp -r skill/sync-team ~/.claude/skills/Then use /sync-team in Claude Code to walk through the full sync flow.
Development
git clone https://github.com/troylar/devsync-mcp
cd devsync-mcp
pip install -e ".[dev]"
pytestLicense
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/troylar/devsync-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server