MCP Readiness
Verify that MCP config files exist and provider tokens are present — distinguish config problems from auth problems.
Steps
- Check config files — verify MCP configuration files exist in expected locations
- Check provider tokens — confirm required environment variables or auth tokens are set
- Classify problems — config missing vs auth missing vs both
- Report next fix — smallest action to reach a working state
Output
Config: found | missing (<path>)
Auth: OK | missing (<provider>)
Status: ready | blocked
Action: <next fix>
Rules
- Never expose secret values or tokens
- Never claim MCP readiness if auth is still missing
- Distinguish config problems from auth problems explicitly
- Report the smallest next fix, not a full setup guide