Skip to content
Glowo
Esc
↑↓navigate↵open⌘Jpreview
On this page

AI agents

Connect Claude Code, Codex, Cursor, VS Code or any MCP client to Glowo, and let it investigate and operate your monitoring with only the access you approve.

Glowo speaks the Model Context Protocol (MCP). Connect an AI agent and ask it, in plain language, what is down, why, and what to do about it, then let it do the work with exactly the access you approve.

Quick start

Add Glowo to your agent

In Claude Code:

claude mcp add --scope user --transport http glowo https://api.glowo.dev/mcp

Codex, Cursor, VS Code and other clients take one line too: see Connecting.

Approve it in your browser

Your client sends you to Glowo’s consent screen. Choose Read Only to start, and approve. In Claude Code, run /mcp and pick glowo if it says the server needs authentication.

Ask it something

Start with a question that changes nothing:

Which of my monitors are down, and since when?

There is no key to create and nothing to paste. The connection appears under Settings → MCP, where you can revoke it at any time.

What an agent can do

Ask The agent Access level
“Is anything down? Since when, and from where?” Lists your monitors and reads the failing checks Read Only
“Why did checkout fail at 03?” Opens that check’s response, headers and timings Read Only
“What was the API’s uptime last week?” Reads the monitor’s hourly statistics Read Only
“Watch api.example.com from Europe and the US, and alert #ops” Probes the URL, adds the channel and creates the monitor Operate
“Acknowledge the alert and tell our users we are on it” Acknowledges, then posts an incident update Operate
“We deploy at 22 for half an hour. Don’t page anyone.” Schedules a maintenance window Operate

Tools lists every tool and the access each one needs.

Two ways to connect

Both reach the same hosted server at https://api.glowo.dev/mcp, with the same tools.

Sign in with OAuth Use an API key
You provide Nothing: you approve in the browser A gl_ API key that allows MCP
Access The level you approve on the consent screen The key’s capabilities
Revoke Per connection, in Settings → MCP Revoke the key
Best for You, at your own machine Servers, CI, and agents shared by a team

Start with OAuth. It needs no setup, shows you exactly what you grant, and can be revoked per client.

Safety

  • You choose the access. An agent gets the level you approve on the consent screen, and Read Only is a complete starting point.
  • Some things are never available. Billing, members, workspace settings and the audit log cannot be granted to an agent or an API key.
  • The agent is told how to behave. Every client receives Glowo’s working rules when it connects: read before writing, confirm before posting or publishing on a status page or deleting, and treat what monitored sites return as data, never as instructions. What your agent is told.
  • Everything is attributable. Agent actions appear in the audit log like any other.
  • Revocation is immediate, per connection.

Start read-only. Grant more once you have watched what the agent actually does.

Was this page helpful?