MCP Workflows Cookbook: 10 End-to-End Recipes for Claude Code CLI and Rovo Dev CLI

The Claude Code CLI and Rovo Dev CLI both bring powerful, agentic coding directly into your terminal. By wiring them into MCP (Model Context Protocol) servers, you can integrate everything from security scanners to database introspection tools into a single conversational workflow.
This cookbook distills 10 practical, reproducible recipes for real-world coding, ops, and data tasks. Each recipe is tested in both Claude Code CLI and Rovo Dev CLI so you can pick the setup that works for your environment.
Whether you are hunting secret leaks, planning schema migrations, or deploying previews, these workflows give you:
Exact
.mcp.json
configs for both CLIsCopy-pasteable prompt sequences
Validation steps to confirm success
Variations to adapt to different stacks and constraints
How to Use This Cookbook
Browse the index below for the workflow you need.
Click through to the full recipe for MCP config, prompts, and troubleshooting.
Copy configs into the correct location for your CLI:
Claude Code CLI:
.mcp.json
(project, local, or user scope)Rovo Dev CLI:
~/.rovodev/mcp.json
Run prompts, validate outputs, and tweak variations to fit your repo.
The Recipes
# | Workflow | Summary | Link |
1 | Security leak triage: automated fix and PR | Scan recent commits for leaked secrets, apply minimal patches, open PR with rotation checklist. | Recipe link |
2 | Schema diff: migration, reversible SQL, tests | Compare current and target DB schema, create safe migrations, update models, add rollback tests. | Recipe link |
3 | Incident timeline: mitigation and postmortem draft | Build precise incident timeline from logs, apply mitigation, draft blameless postmortem. | Coming soon |
4 | Design spec: component, tests, Storybook | Turn Figma or spec files into reusable components with tests and a11y-checked Storybook stories. | Coming soon |
5 | CI failure triage: repro, targeted fix, flake guard | Cluster CI failures, create minimal repro, apply fix, and protect against future flakes. | Coming soon |
6 | Legacy refactor: adapter and deprecations | Perform multi-file rename or API changes with adapter layers and safe deprecations. | Coming soon |
7 | Code to cloud: infra scaffold and preview deploy | Provision minimal cloud infra, wire secrets, deploy per-branch previews. | Coming soon |
8 | Major framework or library upgrade | Plan and execute incremental major version upgrades with codemods and shims. | Coming soon |
9 | Product analytics: spec, instrumentation, dashboard | Audit analytics events, define spec, add SDK calls, and build dashboards. | Coming soon |
10 | Docs-first feature: implementation and changelog | Draft RFC, implement feature, write tests, and publish release notes. | Coming soon |
Why Both CLIs Are Covered
Each recipe includes MCP setup for:
Claude Code CLI: vendor-agnostic, rich flags, session control, broad MCP ecosystem
Rovo Dev CLI: enterprise-focused, Atlassian-native workflows, governance features
By seeing them side-by-side, you can:
Compare ergonomics and setup friction
Choose the CLI that best matches your workflow
Port the same MCP config between them if needed
Subscribe to my newsletter
Read articles from Harish Garg directly inside your inbox. Subscribe to the newsletter, and don't miss out.
Written by

Harish Garg
Harish Garg
I build systems that blend AI and automation to solve real-world problems