AI Setup
Set up AI coding tools for your project
Every AI coding assistant — Claude Code, Cursor, GitHub Copilot, Windsurf — works better with project-specific context. But each tool uses different config files, different formats, and different conventions. Caliber scans your codebase once and generates the right configs for every tool.
The fragmented AI tool landscape
AI coding tools are powerful, but setting them up is a mess. Each tool has its own config format:
| Tool | Instructions file | MCP config |
|---|---|---|
| Claude Code | CLAUDE.md | .claude/settings.local.json |
| Cursor | .cursorrules | .cursor/mcp.json |
| GitHub Copilot | copilot-instructions.md | — |
| Windsurf | .windsurfrules | MCP support |
If your team uses multiple AI tools — which most do — you need to create and maintain all of these files separately. That's hours of manual work that quickly goes stale.
How Caliber unifies AI setup
Caliber takes a different approach. Instead of configuring each tool separately, it scans your codebase once and generates configs for every supported AI tool:
- 1Single scan — Caliber reads your project structure, dependencies, source code patterns, and existing documentation
- 2Multi-tool output — generates CLAUDE.md, .cursorrules, copilot-instructions.md, skills, AGENTS.md, and MCP configs all at once
- 3Correct formats — each config file uses the exact format the tool expects (Cursor's bare URL for HTTP MCPs, Claude Code's command format, etc.)
- 4One refresh command —
caliber refreshupdates all configs as your project evolves
$ npm install -g @rely-ai/caliber
$ cd your-project
$ caliber init
# Configs generated for Claude Code, Cursor, Copilot, and more
Tool-specific setup guides
Dive deeper into setup for each AI coding tool:
- Claude Code setup — CLAUDE.md, skills, AGENTS.md, MCP servers
- Cursor setup — .cursorrules, .cursor/mcp.json
- MCP server setup — auto-configured for every tool
Share AI setup across your team
AI setup isn't just a solo problem. When one developer configures AI tools, the rest of the team misses out — especially on MCP servers with secrets that can't be committed to git. Caliber solves this with team sync: the first developer pushes their setup, and new developers pull it automatically.
Learn more about what Caliber is and how it works under the hood.
Frequently asked questions
What is AI setup for a coding project?
AI setup means configuring your AI coding assistants — Claude Code, Cursor, GitHub Copilot, Windsurf — with project-specific context. This includes instruction files (CLAUDE.md, .cursorrules), MCP server configurations, skills, and agent definitions. Without setup, AI tools generate generic code that doesn't match your project.
Which AI coding tools does Caliber support?
Caliber supports Claude Code (CLAUDE.md, skills, AGENTS.md, .claude/settings.local.json), Cursor (.cursorrules, .cursor/mcp.json), GitHub Copilot (copilot-instructions.md), and Windsurf. It generates the correct config format for each tool from a single codebase scan.
Is AI setup different for each tool?
Yes. Each AI coding tool uses different config files and formats. Claude Code reads CLAUDE.md and .claude/settings.local.json. Cursor reads .cursorrules and .cursor/mcp.json. Copilot reads copilot-instructions.md. Caliber handles these differences automatically — one scan generates configs for every tool.
How do I set up AI tools for a team?
Caliber generates configs that can be committed to git (CLAUDE.md, .cursorrules, skills) so the whole team gets them. For MCP server configs that contain secrets, Caliber provides team sync — the first developer pushes their setup, and new developers pull it automatically with 'caliber init'.
Set up every AI coding tool in 30 seconds.
Get Started