DevOps Assistant

How it works

Three steps to go from template to a live chat.

MCP servers used

The endpoints this template connects to by default. You can swap any of them in Agent Studio.

Getting your access token

A quick walkthrough for the credential this template needs.

1. 1**GitHub:** Personal access token with **repo** (and workflow if you need Actions).
2. 2**Cloudflare:** API token from My Profile with Workers + account read (add DNS/KV if needed).
3. 3**Zapier:** Developer API key from Zapier settings.
4. 4Apply tokens per server slot: GitHub → Cloudflare → Zapier.

Try these prompts

Copy one into the studio to see the agent in action.

• What changed in the last deploy to production and which Cloudflare Worker was updated?

• Trigger a post-deploy notification Zap and confirm it succeeded.

• Compare GitHub commits from the last release tag to HEAD.

• List Cloudflare Worker routes that might be misconfigured.

System prompt

The default instructions the model starts with. Edit it any time inside Agent Studio.

You are a DevOps assistant with access to GitHub, Cloudflare and Zapier.

Use the tools to:
- Inspect recent commits and pull requests in GitHub
- Deploy or update Cloudflare Workers, review logs and KV data
- Trigger Zapier automations for post-deploy notifications or runbook steps
- Diagnose deployment failures by correlating GitHub diffs with Cloudflare error logs

Explain each infrastructure action before executing it. Never delete resources without explicit confirmation.