Team Sync

Sync AI tool configs across your team

When one developer sets up AI coding tools for a project, the rest of the team misses out. MCP servers with API keys can't be committed to git. Skills and agent configs get lost on individual machines. New developers join and start from scratch. Caliber solves this by capturing the first developer's setup and distributing it to everyone.

The problem: AI configs don't travel with the code

Your team has spent time configuring AI tools — connecting MCP servers for database access, setting up deployment tools, adding API documentation sources. But these configs live in local files that aren't shared:

MCP server configs contain API keys and tokens — they can't go in git
User-level settings like ~/.claude/settings.json are per-machine and invisible to teammates
New developer onboarding means hours of “ask the senior dev what MCP servers to install”
Config drift — each developer ends up with a slightly different AI tool setup

How Caliber team sync works

Caliber separates AI configs into two categories and handles each appropriately:

Git-safe configs (committed to the repo)

These files contain no secrets and are shared with every developer through git:

CLAUDE.md — project instructions for Claude Code
.cursorrules — project conventions for Cursor
.claude/skills/ — reusable prompt templates
AGENTS.md — agent definitions

Secret configs (synced through Caliber)

MCP server configs with API keys are synced separately:

.claude/settings.local.json — Claude Code MCP servers (gitignored)
.cursor/mcp.json — Cursor MCP servers (gitignored)

The team sync flow

1First developer runs caliber init — Caliber scans the codebase, generates configs, and pushes MCP setups to Caliber's sync
2Git-safe configs get committed — CLAUDE.md, .cursorrules, skills, and AGENTS.md are in the repo for everyone
3New developer clones the repo and runs caliber init — Caliber detects the existing project, shows available MCP servers, and installs them in the correct format for their AI tool
4Everyone stays in sync — running caliber sync pulls the latest MCP configs from the team

# First developer

$ caliber init

# New developer (after git clone)

$ caliber init

# MCP servers detected — install them? [Y/n]

What gets synced

Caliber handles the full spectrum of AI tool configs. Instruction files and skills travel through git. MCP servers and secrets travel through Caliber's sync. The result: every developer on your team has the same AI tool setup, regardless of when they joined or which editor they use.

Get started with AI setup for your project, or see tool-specific guides for Claude Code and Cursor.

Frequently asked questions

How do I share AI tool configs with my team?

Run 'caliber init' in your project. Caliber generates config files like CLAUDE.md, .cursorrules, and skills that get committed to git — every developer gets them automatically. For MCP server configs with secrets, Caliber syncs them separately so new developers can pull them with 'caliber init' without the secrets ever touching git.

Are MCP server secrets synced safely?

Yes. MCP server configurations that contain API keys or tokens are never committed to git. Caliber syncs them through its own secure channel. When a new developer runs 'caliber init', they receive the MCP configs with the correct format for their AI tool (Claude Code or Cursor) and can provide their own credentials.

Does team sync work with Claude Code and Cursor?

Yes. Caliber generates tool-specific configs for each developer based on their editor. Claude Code users get .claude/settings.local.json, Cursor users get .cursor/mcp.json. The shared configs (CLAUDE.md, .cursorrules, skills) work across both tools. Everyone gets the right format automatically.

Share AI tool configs across your team in minutes.

Get Started