Context
While updating the Tarotscript repo to @stackbilt/cli@1.0.0, I wired Charter into the repo MCP config manually:
"charter": {
"command": "charter",
"args": ["serve", "--name", "tarotscript", "--ai-dir", ".ai"],
"cwd": "/mnt/c/Users/kover/Documents/tarotscript"
}Validation passed:
charter --version -> charter v1.0.0npx charter --version -> charter v1.0.0charter doctor --adf-only --ci --format json -> PASScharter serve --name tarotscript --ai-dir .ai starts the stdio MCP transport and loads the expected ADF modules.
Improvement
Charter has the right primitive with charter serve, but the client setup path still requires hand-editing .mcp.json and knowing the exact command shape. It would be useful for Charter to provide a first-class setup/check workflow for MCP client wiring.
Suggested shape:
charter setup --mcp --client codex|claude|cursor- or
charter mcp install --client codex|claude|cursor
- or a
charter doctor --mcp check that detects whether the current repo is wired into known MCP client configs.
The command should probably emit deterministic JSON and support --dry-run, so repos can review the generated server entry before writing it.
Why this matters
ADF/Charter is becoming the routing standard for repo agent instructions. If charter serve is the bridge into MCP clients, the install path should be as standard as charter doctor: discoverable, repeatable, and easy to verify in CI or local setup.
Extra diagnostic ask
It would also help if charter serve had a lightweight startup self-check for required MCP runtime files/dependencies, with actionable output. During Tarotscript validation, the global install path was the most reliable command path; an explicit diagnostic would make local/package-manager install issues easier to distinguish from ADF or MCP configuration problems.
Context
While updating the Tarotscript repo to
@stackbilt/cli@1.0.0, I wired Charter into the repo MCP config manually:Validation passed:
charter --version->charter v1.0.0npx charter --version->charter v1.0.0charter doctor --adf-only --ci --format json-> PASScharter serve --name tarotscript --ai-dir .aistarts the stdio MCP transport and loads the expected ADF modules.Improvement
Charter has the right primitive with
charter serve, but the client setup path still requires hand-editing.mcp.jsonand knowing the exact command shape. It would be useful for Charter to provide a first-class setup/check workflow for MCP client wiring.Suggested shape:
charter setup --mcp --client codex|claude|cursorcharter mcp install --client codex|claude|cursorcharter doctor --mcpcheck that detects whether the current repo is wired into known MCP client configs.The command should probably emit deterministic JSON and support
--dry-run, so repos can review the generated server entry before writing it.Why this matters
ADF/Charter is becoming the routing standard for repo agent instructions. If
charter serveis the bridge into MCP clients, the install path should be as standard ascharter doctor: discoverable, repeatable, and easy to verify in CI or local setup.Extra diagnostic ask
It would also help if
charter servehad a lightweight startup self-check for required MCP runtime files/dependencies, with actionable output. During Tarotscript validation, the global install path was the most reliable command path; an explicit diagnostic would make local/package-manager install issues easier to distinguish from ADF or MCP configuration problems.