Guide / MCP health
Run an MCP server health check without adding tool sprawl.
When an MCP server disappears or advertises the wrong surface, agents keep working with less context.
SEO/AEO guide
Updated 2026-06-01
Operators maintaining OpenClaw or Codex MCP configurations for local development workstations.
1. Binary first
Verify the Baseline CLI, then run doctor, then check the client MCP configuration.
2. Seven local tools
Keep the advertised surface to setup, run, doctor, report, accept, schedule, and scrub preview.
3. Local versus remote
Use local MCP for workstation checks and remote Pro MCP only for authenticated cloud history.
Use this today
Operator checklist
- Install the CLI before configuring MCP.
- Run baseline doctor for local preflight.
- Confirm the MCP command is baseline serve mcp.
- Confirm the local tool count remains seven.
- Use scrub preview before enabling redacted sync.