Connect Cloudflare Observability to OpenCode
Give OpenCode governed access to Cloudflare Observability through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Cloudflare Observability to OpenCode in four steps
Admins approve the server once. Everyone in OpenCode then gets it through the same governed connection.
- 1
Approve Cloudflare Observability in Runlayer
Add Cloudflare Observability from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect OpenCode to Runlayer
Users add the Runlayer Plugin to OpenCode by hand using Runlayer’s generic MCP steps. OpenCode reaches Cloudflare Observability’s tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
OpenCode setup guide - 3
Sign in to Cloudflare Observability
Sign in the way Cloudflare Observability requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Cloudflare Observability from OpenCode
Cloudflare Observability’s approved tools appear in OpenCode. Every call is checked against policy and recorded.
Tools
Cloudflare Observability tools in OpenCode
Cloudflare Observability reports its tools when your organization connects it, so the list depends on your deployment.
Control
What Runlayer can see and stop in OpenCode
Some controls apply to every client at the gateway. Others depend on what OpenCode exposes to Runlayer.
Gateway policy (available)
Every Cloudflare Observability call from OpenCode passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, OpenCode as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for OpenCode yet, so control happens at the gateway.
Frequently asked questions
Connect more