# devglow (npm · devglow-mcp)

Start, stop, and inspect local dev servers in a desktop app instead of the agent's session.

- Trust score: 81/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- npm · `devglow-mcp`: 81/100 (this document), [markdown](https://verifymcp.io/servers/app-devglow-devglow/devglow-mcp.md), [page](https://verifymcp.io/servers/app-devglow-devglow/devglow-mcp)

## Channel facts

- Registry: `npm`
- Package: `devglow-mcp`
- Version: `1.3.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2345 tokens (~180/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_project" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the devglow MCP server?

devglow runs locally as an npm package, launched with npx -y devglow-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add app-devglow-devglow -- npx -y devglow-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "app-devglow-devglow": {
      "command": "npx",
      "args": [
        "-y",
        "devglow-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-devglow-devglow": {
      "command": "npx",
      "args": [
        "-y",
        "devglow-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add app-devglow-devglow -- npx -y devglow-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-devglow-devglow": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "devglow-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-devglow-devglow --command npx --arg -y --arg devglow-mcp
```

### Hermes

```yaml
mcp_servers:
  app-devglow-devglow:
    command: "npx"
    args: ["-y", "devglow-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "app-devglow-devglow": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "devglow-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-devglow-devglow -t stdio -c npx -a -y devglow-mcp
```

### Other

```json
{
  "mcpServers": {
    "app-devglow-devglow": {
      "command": "npx",
      "args": [
        "-y",
        "devglow-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-24 (score 81, 0)

- [security] Stability: 0.97 → pass

### 2026-09-23 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 79, −2)

- [functional] Stability: pass → 0.80

### 2026-09-17 (score 81, 0)

- [security] Stability: 0.97 → pass

### 2026-09-16 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 79, −2)

- [functional] Stability: pass → 0.80

## MCP tools (13)

### `list_projects` (~21 tokens)

List all projects

List all registered user projects and AI temporary processes with their status.

### `get_status` (~32 tokens)

Get project status

Get the running status of a specific project or AI process.

Input parameters:

- `id` (string, required): Project or AI process ID

### `get_project` (~78 tokens)

Get full project details

Get the full metadata for a single project or AI process (path, command, port, tags, description, status). Use this when you need details beyond what list_projects shows — for example, to duplicate a project with the same path or read its description before editing.

Input parameters:

- `id` (string, required): Project or AI process ID (from list_projects)

### `get_logs` (~50 tokens)

Get process logs

Export and retrieve recent logs from a running or stopped process.

Input parameters:

- `id` (string, required): Project or AI process ID
- `lines` (number): Number of recent lines to return (default: 100)

### `check_port` (~71 tokens)

Check port availability

Check if a TCP port is in use on localhost. When occupied, also reports who holds it — and if it's a devglow-managed project (so the user can recognize their own process). Call this BEFORE run_process / create_project to avoid silent conflicts.

Input parameters:

- `port` (number, required): Port number to check

### `start_project` (~80 tokens)

Start a registered project

Start a user-registered project using its configured command (cannot modify the command). PREFER this over run_process: call list_projects first, and if a project for this path/command already exists, start it here instead of re-running it yourself. This reuses the command the user registered.

Input parameters:

- `id` (string, required): Project ID (from list_projects)

### `stop_project` (~28 tokens)

Stop a project

Stop a running project or AI process.

Input parameters:

- `id` (string, required): Project or AI process ID

### `run_process` (~242 tokens)

Run a new AI process

Create and start ONE new temporary process. Shows in DevGlow's AI Processes section. User can later [keep] or [dismiss] it. Before calling this, run list_projects: if the user already registered a project for this path/command, call start_project instead so you run THEIR command, not a new one. Only use run_process when no matching project exists. If you are starting more than one process, call workspace_run once instead of calling this repeatedly — otherwise each process waits in the sidebar and the user sees nothing happen.

Input parameters:

- `command` (string, required): Shell command to execute
- `description` (string): Short summary of what the app does (max 280 chars). Helps the user remember the project later. Write 1-2 plain sentences from the user's perspective.
- `name` (string, required): Display name for the process. Do NOT include port number in the name — use the port parameter instead.
- `path` (string, required): Working directory (supports ~/)
- `port` (number): Port number the process will listen on. Check package.json scripts or config files for --port flags. Important for DevGlow to show the correct port badge.

### `update_project` (~264 tokens)

Update a project's metadata

Update a kept (permanent) DevGlow project's metadata. Pass only the fields you want to change. Does NOT apply to temporary AI processes — for those, set fields at run_process time or have the user keep the process first.

Input parameters:

- `command` (string): New shell command.
- `description`: Short summary (max 280 chars). Pass null or empty string to clear.
- `id` (string, required): Project id (call list_projects first). Must be a permanent project, not an AI process (those have ids starting with 'ai-').
- `interactive` (boolean): Toggle PTY (interactive terminal) mode. true = run through a pseudo-terminal so tools like flutter run / expo start accept hot reload (r) / restart (R) keys; false = plain pipe. Only set when the use…
- `name` (string): New display name.
- `path` (string): New working directory (supports ~/).
- `port` (number|null): New port number. Pass null to clear the existing port.
- `tags` (array): Tags as a list of strings. Pass [] to clear. Do NOT invent tags; only set this when the user explicitly asks, or when reusing an existing tag visible in list_projects.

### `create_project` (~351 tokens)

Create a permanent project (without running)

Register a permanent DevGlow project WITHOUT running it. This is how you 'add a project to DevGlow' — there is no config file to author (no devglow.json / DEVGLOW.md); calling this tool IS the registration. Use it for bulk registration when you want to record metadata only (no port binding, no browser tab, no dependency install). To start the project later, call start_project. Use run_process instead when you need to actually launch a server for verification or one-off work.

Input parameters:

- `command` (string, required): Shell command to run when the user starts the project.
- `description` (string): Short summary of what the app does (max 280 chars).
- `interactive` (boolean): Run in a PTY (interactive terminal) so tty-driven tools like `flutter run` / `expo start` enter interactive mode and accept key input (hot reload r, restart R). DEFAULT: omit — the command is auto-de…
- `name` (string, required): Display name.
- `path` (string, required): Working directory (supports ~/).
- `port` (number): Port number the command listens on, if any. Used for the Open ↗ button.
- `tags` (array): Tags. DEFAULT: omit (no tags). Tags are the user's manual grouping system — do NOT auto-fill with technology guesses (e.g., 'db', 'test', 'api'). Only set this when the new project clearly belongs to…

### `delete_project` (~64 tokens)

Delete a permanent project

Delete a kept (permanent) DevGlow project. Stops the process if running. Does NOT apply to AI processes — those are dismissed via the UI.

Input parameters:

- `id` (string, required): Project id (call list_projects first). Must be a permanent project, not an AI process.

### `stop_process` (~27 tokens)

Stop an AI process

Stop a running AI temporary process by name.

Input parameters:

- `name` (string, required): AI process name

### `workspace_run` (~239 tokens)

Run processes in a new workspace

Start two or more processes and arrange them on screen together in a new DevGlow workspace. PREFER this over repeated run_process calls whenever you are starting more than one process — the user does not have to ask to see them. Repeated run_process calls leave each process sitting in the sidebar until the user clicks it into a pane, so starting three that way makes the app look like nothing happened. Each process here starts exactly as run_process would. Always creates a new workspace: a name that already exists gets a numbered variant, and no existing workspace is ever modified, so a repeat call cannot disturb the user's arrangement. DevGlow chooses the split layout from its own window size; you cannot specify one. If DevGlow is closed it will be launched.

Input parameters:

- `name` (string, required): Name for the new workspace, as the user will see it in the sidebar. Describe the group, not one process (e.g. 'api stack', 'checkout debug').
- `processes` (array, required): Processes to start, in the order they should appear on screen. Panes beyond DevGlow's 8-pane cap still run; they just wait in the sidebar.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/app-devglow-devglow/devglow-mcp#diagnostics

## Score history

- 2026-09-24: 81
- 2026-09-23: 81
- 2026-09-22: 80
- 2026-09-21: 80
- 2026-09-20: 80
- 2026-09-19: 79
- 2026-09-18: 79
- 2026-09-17: 81
- 2026-09-16: 81
- 2026-09-15: 80
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 81
- 2026-09-09: 81
- 2026-09-08: 80
- 2026-09-07: 80
- 2026-09-06: 80
- 2026-09-05: 79
- 2026-09-04: 79
- 2026-09-03: 78
- 2026-09-02: 78
- 2026-09-01: 77
- 2026-08-31: 77
- 2026-08-30: 76
- 2026-08-29: 76
- 2026-08-28: 75
- 2026-08-27: 75
- 2026-08-26: 74

## Common questions

### What is the devglow MCP server?

devglow is an MCP server listed in the public MCP registry as app.devglow/devglow. Start, stop, and inspect local dev servers in a desktop app instead of the agent's session. This page covers its npm package (devglow-mcp).

### Is the devglow MCP server safe to use?

devglow scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the devglow MCP server expose?

devglow exposes 13 tools: list_projects, get_status, get_project, get_logs, check_port, and 8 more. Their descriptions and schemas cost roughly 1,547 tokens of context every time the server is loaded.

### Is the devglow MCP server still maintained?

devglow is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the devglow MCP server under?

devglow declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/devglow-mcp
- Socket report: https://socket.dev/npm/package/devglow-mcp
- Repository: https://github.com/aesopfrom0/devglow-releases
- Website: https://devglow.app/devglow
- Changelog RSS feed: https://verifymcp.io/servers/app-devglow-devglow/devglow-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-devglow-devglow/devglow-mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-devglow-devglow/devglow-mcp