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.
Install
pip install devsync-mcp
MCP Configuration
Add to your IDE's MCP settings:
{
"mcpServers": {
"devsync-mcp": {
"command": "devsync-mcp",
"transport": "stdio"
}
}
}
Tools
| Tool | Purpose |
|---|---|
pull_team_profile |
Clone/pull team config repo |
list_profile_configs |
List configs in a profile |
detect_current_configs |
Scan environment for existing configs |
preview_merge |
Return source + target for LLM merge |
apply_merge |
Write merged content with backup |
sync_all |
Pull latest + present merge plan |
list_backups |
List previous merge backups |
restore_backup |
Restore from backup |
get_merge_status |
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 backup
Team 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 Code
Config 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]"
pytest
License
MIT
Metadata
Release files for devsync-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| devsync_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / devsync_mcp-0.1.0-py3-none-any.whl
| Download URL | devsync_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 17.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d1c53003717914242b3b55b03c864204ae2120b330a9527d833ed81431d688fc
|
|
BLAKE2b-256 checksum How to use checksums |
2b7cd96d567e38c5121221173b9937c8ed772c8b11596531aa27b13a2ed63056
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 15, 2026.
Transparency log