1. Conduid
  2. Developer Tools
  3. Devsync MCP
MCP server · Developer Tools

Devsync MCP

MCP server for AI-merge of team dev configurations

Unclaimed MIT last commit 8 months ago devtools
56Fair

Scored 13 days ago · breakdown

About Devsync MCP

Devsync MCP is an MCP server published by troylar in the Developer Tools category: mCP server for AI-merge of team dev configurations.

Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/troylar/devsync-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Tools (9)

apply_mergeWrite merged content with backup

Parameters not published.

detect_current_configsScan environment for existing configs

Parameters not published.

get_merge_statusShow merged/pending/changed status

Parameters not published.

list_backupsList previous merge backups

Parameters not published.

list_profile_configsList configs in a profile

Parameters not published.

preview_mergeReturn source + target for LLM merge

Parameters not published.

pull_team_profileClone/pull team config repo

Parameters not published.

restore_backupRestore from backup

Parameters not published.

sync_allPull latest + present merge plan

Parameters not published.

Ask AI

✦

Ask AI about Devsync MCP

Powered by Claude · Grounded in docs

I know everything about Devsync MCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

3 checks have not been run yet.

Releases

v0.1.0v0.1.0 · 15 Feb 2026devsync-mcp v0.1.0 Initial release of the MCP server for AI-merge of team dev configurations. Features 9 MCP tools for full merge workflow AI-powered merging — server provides source + target content; your IDE's LLM performs the…

README

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, .profile
  • git_config — .gitconfig, .gitignore_global
  • editor_config — .editorconfig
  • ai_rules — CLAUDE.md, .cursorrules, AGENTS.md, etc.
  • vscode_settings — .vscode/settings.json, etc.
  • ssh_config — .ssh/config
  • custom — 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

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About Devsync MCP

How do I install Devsync MCP?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Devsync MCP safe to use with an AI agent?

Its trust score is 56 out of 100 (fair). It passes 2 of the 3 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Devsync MCP still maintained?

The last commit was 8 months ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.