Show Notes
We cut through the noise to show how to install MCPs for Claude Code, where the config can live, and what to watch out for with Claude Code.
MCP config locations
- Project level: settings.local.json
- Cloud folder: the dedicated cloud config area
- On Mac: reveal hidden dotfiles with Command+Shift+. to see these paths
How to install MCPs (step-by-step)
- In Claude Code, search for the MCP provider you want (example: convex MCP server).
- Open the provider and copy the exact convex object snippet.
- Paste or paste-and-apply that convex object into your MCP provider config.
- Verify the MCP is wired up and running from the provider view.
Claude Code caveats
- Don’t rely on Claude Code to set up MCPs; it can mess things up.
- Early Claude Code setups may pass arguments that don’t work in practice.
- Documentation tends to focus on interactive mode; headless workflow is likely the future (hooks and headless changes are worth watching).
Tips and resources
- There’s a helpful reference site for MCP setup: claudlog.com
- A good thread by Dave on looping tests and piping results into a fixer script can be useful for automation (check his Twitter).
- If you want deeper context, check Claude Code docs and notes on headless vs interactive modes.
Actionable quick-start checklist
- Locate your MCP config location (project settings.local.json or cloud folder).
- Find the Convex MCP server provider and copy the convex object.
- Apply the convex object to the MCP provider config.
- Test locally and guard against Claude Code quirks (avoid relying on its setup flow).
Links
- Claudlog
- Claude Code docs (headless vs interactive, hooks)
- Model Context Protocol
- Convex (backend platform with MCP support)