devglow MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Devglow local development-process control: Does agent-controlled start/stop remain scoped to registered processes rather than arbitrary shell execution?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Start, stop, restart and inspect local development servers outside the agent's own shell session.

What we know

devglow is a desktop process manager for development commands; its MCP lets coding agents drive registered local servers, inspect logs and diagnose port conflicts while server lifetimes remain in the desktop app.

Maintenance / activity evidence

devglow-mcp 1.4.0 published 2026-10-03T04:22:20.932Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Control over registered local development commands/processes. Writes: Start/stop/restart registered shell commands.
Authentication not yet verified.
Sensitive access: Development logs, Local environment/process context

Command execution is intentionally bounded to configured dev servers but still has local process authority.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Does agent-controlled start/stop remain scoped to registered processes rather than arbitrary shell execution?

The bounded review of the publisher's documented Devglow local development-process control and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Command execution is intentionally bounded to configured dev servers but still has local process authority.
Control over registered local development commands/processes.
Logs/process output remain on local workstation unless client transmits them.
Reviewed write actions: Start/stop/restart registered shell commands
Sensitive access: Development logs, Local environment/process context
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
exact MCP package configuration
desktop permission/scoping details
It can execute commands previously registered in the desktop app.
Local command/log authority can expose secrets printed by development processes.
Exact package configuration and permission model were not fully documented in the public page.

Original activity observations

devglow-mcp 1.4.0 published 2026-10-03T04:22:20.932Z

Technical identity

npm/devglow-mcp

Exact implementation source: https://www.npmjs.com/package/devglow-mcp ↗
Reviewed resource type: Host
Package identity: npm:devglow-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
devglow-mcp
Recorded package identity, distribution or download evidence.
Evidence source ↗
devglow.app/
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Host / Desktop app setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Publisher warns bare npx spec can select bad cached copy; host process tools can access local development runtime
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / launch application
Publisher instructions
Publisher warns bare npx spec can select bad cached copy; host process tools can access local development runtime | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Claude Code only · Publisher instructions
claude mcp add -s user devglow -- npx -y --prefer-offline devglow-mcp@latest
Configure application / integrations
MCP100 setup guide
Codex `codex mcp add devglow -- npx -y --prefer-offline devglow-mcp@latest`; supports HTTP mode separately.
Check connection
Suggested check
Inspect get_status/list_projects tool responses without changing projects.
Disconnect / uninstall / revoke
MCP100 setup guide
If registered by the publisher Claude Code example under `devglow`, run the provided unregister command; for a different MCP client or name, delete the actual client registration. Removing a local client entry is distinct from deleting a vendor account/token.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove devglow

Official Documentation & Sources

What it does

devglow is a desktop process manager for development commands; its MCP lets coding agents drive registered local servers, inspect logs and diagnose port conflicts while server lifetimes remain in the desktop app.

Capability: Developer Tools
Resource type: Host
Best fit: Start, stop, restart and inspect local development servers outside the agent's own shell session.

Representative uses

Start/stop/restart dev servers
Inspect logs
Detect port conflicts
Keep long-running servers alive outside agent session

Limitations

It can execute commands previously registered in the desktop app.
Local command/log authority can expose secrets printed by development processes.
Exact package configuration and permission model were not fully documented in the public page.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Control over registered local development commands/processes.
Data handling: Logs/process output remain on local workstation unless client transmits them.
Cost: one_time_or_desktop_license
Risk and cautions: Command execution is intentionally bounded to configured dev servers but still has local process authority.

Access scope and cautions

Write actions: Start/stop/restart registered shell commands
Sensitive access: Development logs Local environment/process context
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Start/stop/restart dev servers; Inspect logs; Detect port conflicts; Keep long-running servers alive outside agent session.

What authentication is documented?

Local devglow desktop/app trust boundary; no cloud credential established.

Can it modify data or perform write operations?

Documented write actions include: Start/stop/restart registered shell commands. Recorded permission boundary: Control over registered local development commands/processes.

What data-handling boundary should I consider?

Logs/process output remain on local workstation unless client transmits them. Recorded sensitive-access context: Development logs; Local environment/process context.

What limitations and risks should I check before use?

Command execution is intentionally bounded to configured dev servers but still has local process authority. It can execute commands previously registered in the desktop app. Local command/log authority can expose secrets printed by development processes. Exact package configuration and permission model were not fully documented in the public page. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is one time or desktop license. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.