Claude Code — Platform Details
Claude-specific configuration: MCP enablement, permissions, settings scope, and customization.
Prerequisites
Complete Steps 1–3 on the Setup page first (install plugins, init, scan).
Environment variables (AEM_INSTANCES, AXE_API_KEY, etc.) are documented there.
MCP Server Configuration
Claude Code reads .mcp.json at the project root — created by /dx-init.
ADO MCP — Auto-Configured
Browser-based OAuth. On first use, opens a browser to authenticate. No PAT or env var needed.
AEM + Chrome DevTools MCP
AEM MCP reads AEM_INSTANCES from your shell. Chrome DevTools auto-launches — just ensure Chrome is installed.
Enable Only What You Need
Unused MCP servers consume tokens. Enable selectively in .claude/settings.json:
{
"enableAllProjectMcpServers": false,
"enabledMcpjsonServers": ["ado"]
} Add “AEM” and “chrome-devtools-mcp” for AEM projects.
Env Vars — Two Options in Claude Code
Claude Code can read env vars from your shell profile (recommended — works for both Claude Code and Copilot CLI)
or from .claude/settings.local.json under “env” (Claude Code only, gitignored).
Shell profile is preferred for portability.
Settings & Permissions
Auto-configured by /dx-init — documented here for manual setup or troubleshooting.
Settings Scope
| Scope | Stored In | Shared via Git | Use For |
|---|---|---|---|
| project (recommended) | .claude/settings.json | Yes | Permissions, MCP enablement, attribution |
| local | .claude/settings.local.json | No (gitignored) | Secrets, personal env vars |
| user | ~/.claude/settings.json | No | Global preferences |
Permissions
Start minimal, expand as needed — Claude prompts for anything not in the allow list:
{
"permissions": {
"allow": [
"Bash(git:*)",
"Bash(npm:*)",
"Bash(npx:*)",
"Bash(mvn*)",
"mcp__ado__wit_get_work_item",
"mcp__ado__wit_list_work_item_comments",
"mcp__ado__search_code"
]
}
} Avoid Wildcards
Do not use wildcards like mcp__ado__* — they send full tool schemas on every request, wasting tokens.
Co-authored Commit Footer
Disable Claude’s default co-author footer:
{
"attribution": {
"commit": "",
"pr": ""
}
} Customization
Adjust agent behavior, override config, or shadow entire skills.
Shared Rules
Edit files in .ai/rules/ to change review criteria, answer tone, or pragmatism filters.
Changes apply to both local skills and automation agents.
Config Overrides
Add an overrides: section to .ai/config.yaml:
overrides: pr-review: tone: "direct, no praise" severity-threshold: 80
Skill Shadowing
Override any plugin skill by creating one with the same name in your project. Project-level skills take precedence automatically.
Troubleshooting
Plugins Not Visible?
Check .claude/settings.json for enabledPlugins. Or run /plugin list to verify.
MCP Connection Issues
Run /dx-doctor to validate MCP connections, config, and rule files.
/dx-doctor
Uninstall
claude plugin uninstall dx claude plugin uninstall aem
Project Files Preserved
Project files in .ai/ are not removed — they belong to the project, not the plugin.