Practical Notes
- Setup time ~20 minutes (auth + run server + connect agent)
- Operational check: read-only queries return within 1–2 tool calls, not multi-turn scraping
- GitHub stars + forks (verified): see Source & Thanks
DevOps automation fails when it’s ‘too powerful by default’. Keep your agent on a tight leash: start with read-only triage, then add one write action at a time. If the agent can’t provide a justification (link, run id, work item id), block the write.
FAQ
Q: Why MCP instead of REST calls in the agent? A: MCP gives you a consistent tool contract and a place to enforce auth, logging, and limits.
Q: What should I allow first? A: Start with read-only tools: list pipelines, get run status, list work items.
Q: How do I avoid risky changes? A: Gate write tools behind approvals and limit scopes to one project/team at a time.