Skip to Content
ReferenceMCP support

MCP support

AlignTrue supports Model Context Protocol (MCP) configuration across 14+ AI coding agents. MCP enables AI agents to connect to external tools, data sources, and services through a standardized protocol.

What is MCP?

Model Context Protocol allows AI agents to:

  • Access external tools and resources
  • Integrate with project-specific services
  • Extend agent capabilities beyond training data
  • Connect to custom APIs and data sources

AlignTrue automatically generates agent-specific MCP configuration files from your rules, ensuring consistent tool access across your development workflow.

Supported MCP agents

AlignTrue exports MCP configuration for 14 agents across 6 format types:

JSON-based MCP configurations

AgentExporterConfig FileNotes
GitHub Copilotvscode-mcp.vscode/mcp.jsonVS Code integration
Cursorcursor-mcp.cursor/mcp.jsonCursor-specific setup
Claude Coderoot-mcp.mcp.jsonRoot-level config
Aiderroot-mcp.mcp.jsonShared with Claude Code
Windsurfwindsurf-mcp.windsurf/mcp_config.jsonWindsurf-specific format
Amazon Qamazonq-mcp.amazonq/mcp.jsonAWS integration
Firebase Studiofirebase-mcp.idx/mcp.jsonFirebase IDX platform
KiloCodekilocode-mcp.kilocode/mcp.jsonKiloCode-specific
Roo Coderoocode-mcp.roo/mcp.jsonRoo Code format
Ampamp-mcp.amp/settings.jsonProject-level settings
AugmentCodeaugmentcode-mcp.augment/settings.jsonAugment platform
Kirokiro-mcp.kiro/settings/mcp.jsonKiro settings directory

YAML-based MCP configurations

AgentExporterConfig FileNotes
Goosegoose-mcp.goose/config.yamlYAML format for extensions
Trae AItraeai-mcptrae_config.yamlProject root (git-ignored)

Special MCP handling

AgentExporterConfig FileNotes
Juniejunie-mcp.junie/mcp/mcp.jsonDirectory-based MCP structure

Central MCP configuration

AlignTrue uses a centralized MCP configuration in .aligntrue/config.yaml:

mcp: servers: - name: aligntrue command: npx args: ["-y", "@aligntrue/cli", "mcp-server"] - name: custom-tool command: python args: ["./tools/custom-mcp.py"] env: API_KEY: "${process.env.CUSTOM_API_KEY}"

This central definition is transformed into agent-specific formats automatically.

Exporter capabilities

Each MCP exporter:

  • Reads from centralized config in .aligntrue/config.yaml
  • Generates agent-specific MCP JSON/YAML format
  • Includes content hash for determinism
  • Supports fidelity notes for partial compatibility
  • Handles vendor-specific MCP extensions

Configuration schema

MCP servers require:

  • name (required): Unique identifier (e.g., aligntrue)
  • command (required): Executable command (e.g., npx, python, node)
  • args (optional): Command arguments as array
  • env (optional): Environment variables as object
  • disabled (optional): Temporarily disable without removing config

Format differences

JSON vs YAML

JSON-based (most agents):

  • Consistent structure across platforms
  • Easier parsing and validation
  • Direct MCP protocol representation

YAML-based (Goose, Trae):

  • Human-readable format
  • Easier manual editing
  • Agent-specific customizations

Project-level only

By design, AlignTrue writes MCP configuration only to project-level files:

  • .vscode/mcp.json (not global VS Code settings)
  • .cursor/mcp.json (not global Cursor config)
  • .goose/config.yaml (not global ~/.config/goose/config.yaml)

This approach:

  • Keeps rules version-controlled and reviewable
  • Enables team collaboration on shared MCP config
  • Prevents machine-specific drift
  • Works with monorepos and scoped rules

If you need global MCP configuration, copy the project-level file to your global config location manually.

Fidelity notes

When MCP features cannot be fully represented, exporters include fidelity notes:

{ "fidelity_notes": [ "Section 'Performance': machine-checkable checks not represented in MCP format" ] }

These notes indicate:

  • Information loss during export
  • Unsupported features for this agent
  • Recommendations for manual customization

Determinism

All MCP exports are deterministic:

  • Same input (rules + config) → identical MCP JSON
  • Content hash included for verification
  • Order preserved across exports
  • Reproducible across machines and CI
Last updated on