DevOps

getglow.io

Manages and monitors WordPress websites for an agency, tracking site status, updates, and plugin information.

1 endpoint28 known toolsFirst detected September 9, 2026Last detected September 9, 2026

ENDPOINT 1

https://my.getglow.io/api/mcp

No auth detected

MCP server metadata

Name: glow-wordpress
Version: 0.1.0

Capabilities

tools

Known tools 28

fleet_overview

One summary of the whole estate: site counts, uptime, outstanding plugin, theme and core updates, report and backup coverage, a ranked list of sites needing attention, and vulnerable sites.

Inferred read-only

find_sites

Search this agency's websites by domain, site name or client name.

Inferred read-only

find_plugin

Which websites have a given plugin or theme installed, and at what version.

Inferred read-only

list_websites

Websites in this agency, optionally narrowed to one client.

Inferred read-only

pending_updates

Plugin, theme and core updates outstanding across the fleet, one client, or one website, ordered by the most outstanding first.

Inferred read-only

site_updates

The plugins and themes with an update outstanding on ONE website, named individually with their current and available versions.

Potential side effects

connection_issues

Websites that are not currently connected to Glow: never connected, disconnected, or erroring.

Inferred read-only

vulnerabilities

Known vulnerabilities affecting sites in this agency, from the vulnerability feed matched against each site's recorded plugin and theme versions.

Inferred read-only

list_backups

Backup runs and restore points for one website, or the latest backup per site across a client or the fleet.

Inferred read-only

performance

PageSpeed scores and load times recorded for sites in this agency, desktop and mobile.

Inferred read-only

site_timeline

Actions taken on sites in this agency: updates run, tickets resolved, work logged, with who did it and when.

Inferred read-only

list_reports

Reports already generated for one website: the period covered, when it was generated, its size, whether it was emailed successfully, and a temporary download link.

Inferred read-only

report_schedule

Report configuration across the fleet, one client, or one website: whether a report is set up at all, how often it runs, when it next runs, who receives it, and which sections are included.

Inferred read-only

uptime_history

Downtime incidents for one website, newest first, with the reason and HTTP status where known, plus the uptime percentage over a recent window.

Inferred read-only

ssl_status

Certificate expiry dates for monitored websites, soonest first.

Inferred read-only

time_summary

Hours logged against websites over a period, per site, from the work recorded in Glow.

Inferred read-only

whats_changed

Everything that happened across the estate since a date: work carried out, updates applied, and sites that went down or recovered.

Inferred read-only

pending_today

One work queue across the whole estate: reports due to send, sites needing attention, sites with the most outstanding updates, backups that failed, and sites that are down.

Potential side effects

list_resellers

Reseller agencies beneath this developer agency, with how many clients and websites each has.

Inferred read-only

site_login_link

A link that takes the agency into a website's WordPress admin, signed in, via Glow.

Inferred read-only

time_allowance

For each website: the monthly custom-development allowance, how many minutes have been logged against it this calendar month, and how much is left.

Inferred read-only

add_website_guide

The steps to connect a new WordPress site to Glow, with the agency's own dashboard link and how many sites it currently manages.

Inferred read-only

run_safe_update

Update named plugins on ONE website using Safe Updates, which takes a backup and screenshots first, verifies the site afterwards, and can be rolled back.

Potential side effects

run_update

Update named themes, or WordPress core, on ONE website.

Potential side effects

safe_update_status

Progress of safe updates on one website: which plugins are being updated, what stage each has reached, and when it was last touched.

Inferred read-only

set_uptime_monitoring

Enable or disable uptime monitoring for ONE website.

Inferred read-only

add_custom_work

Record a piece of work against ONE website, so it appears on the timeline and in the client report.

Inferred read-only

set_time_allowance

Set how many hours of custom development time are allowed for ONE website each month.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.glow-wordpress]
url = "https://my.getglow.io/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "glow-wordpress": {
      "type": "http",
      "url": "https://my.getglow.io/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: glow-wordpress
Remote MCP URL: https://my.getglow.io/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "glow-wordpress": {
      "url": "https://my.getglow.io/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "glow-wordpress": {
      "type": "http",
      "url": "https://my.getglow.io/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "glow-wordpress",
  "transport": "streamable-http",
  "url": "https://my.getglow.io/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.