AI Configuration Setup
@kevinjalbert
Centralized management of AI tool configurations (rules, commands, MCP servers) with streamlined setup for global and project-specific environments.
Overview
What is AI Configuration Setup?
AI Configuration Setup is a command-line tool that simplifies the management of AI configurations—rules, commands, and MCP servers—across multiple AI coding assistants. It allows developers to maintain a single source of truth for their AI settings and easily propagate them to both global and project-specific locations. The tool currently supports Copilot (global scope), Claude Code (global scope), and Cursor (project scope).
How to use AI Configuration Setup?
Create a configuration directory (~/ai_configs by default, overridable with the AI_CONFIGS_DIR environment variable) containing rules (.mdc files), commands (.mdc files), and an mcp-servers-config.json file. Run scripts/setup --help to see available options, then run scripts/setup with appropriate flags to propagate your configuration. Use scripts/reset to remove all symlinks and globally configured files.
Key features of AI Configuration Setup
- Single configuration directory for rules, commands, and MCP servers.
- Supports global scope for Copilot and Claude Code.
- Uses symlinks for Cursor project‑based rules and commands.
- Idempotent setup script safe to run multiple times.
- Marker system for injecting rules into VSCode JSON5 settings.
Use cases of AI Configuration Setup
- Maintain a central source of truth for AI rules across multiple tools.
- Quickly set up project‑specific configurations for Cursor.
- Update MCP server configurations in one place and propagate globally.
- Reset all AI tool configurations to a clean state.
FAQ from AI Configuration Setup
What AI tools are supported?
Copilot, Claude Code, and Cursor are currently supported, each with different scope (global or project) as shown in the README’s feature table.
Does the tool support Windows or Linux?
No. The tool has been built and tested only on macOS; Windows and Linux are not supported at this time.
How does the setup handle Cursor’s lack of global rules?
Cursor only supports project‑based rules. The setup script creates symlinks inside the .cursor/rules/local/ directory of each project, so changes to the central configuration are automatically reflected.
Is the setup script safe to run multiple times?
Yes, the script is designed to be idempotent. Running it repeatedly will not cause issues, making it safe to apply updates or set up new projects.
Can I override the default configuration directory?
Yes. Set the AI_CONFIGS_DIR environment variable before running the setup script to use a different directory instead of ~/ai_configs.