TodoGlow MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Todoglow todo reading and agent-thread progress reports: Do thread updates remain separate from changing the user's todos and preserve desktop-app scope?

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

Best fit

Track coding-agent progress and advance shared task items.

What we know

See what each of your coding agents is working on, and read or advance your todos. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Maintenance / activity evidence

todoglow-mcp 1.1.2 published 2026-08-11T13:11:36.887Z

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Permissions not yet verified. Writes: Advance task statuses (per source description).
Authentication not yet verified.
Sensitive access: Task/project metadata

Potential high-impact side effects: Advance task statuses (per source description).

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

All limitations / Review context

Do thread updates remain separate from changing the user's todos and preserve desktop-app scope?

The bounded review of the publisher's documented Todoglow todo reading and agent-thread progress reports 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.

Potential high-impact side effects: Advance task statuses (per source description).
Reviewed write actions: Advance task statuses (per source description)
Sensitive access: Task/project metadata
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.
repositoryIdentity: no confirmed package-to-repository binding
authentication: exact official auth and credential handling
dataHandling: provider destinations, retention and egress
cost: plans, pay-per-call charges, and payment authorization details
Workspace sharing, auth and precise mutation scope not verified

Original activity observations

todoglow-mcp 1.1.2 published 2026-08-11T13:11:36.887Z

Technical identity

npm/todoglow-mcp

Exact implementation source: https://www.npmjs.com/package/todoglow-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:todoglow-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 ↗
todoglow-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Claude Code only · Publisher instructions
claude mcp add -s user todoglow -- npx -y --prefer-offline todoglow-mcp@latest
Configure / authenticate
MCP100 setup guide
Use desktop companion if required; retain @latest to avoid duplicate npx cache copies.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Check connection
Suggested check
Inspect list_todos or read-only status; do not create/update work items for verification.
Remove / uninstall / revoke
MCP100 setup guide
If registered as `todoglow-mcp` in Claude Code, remove its exact client entry with `claude mcp remove todoglow-mcp`; for Cursor/Claude Desktop/Codex, remove the matching MCP entry in that host settings. This client removal is MCP100-composed, not a vendor uninstall instruction. Npx does not imply a global install; do not delete user data or revoke credentials implicitly.
Publisher install example registration name(s): todoglow. The supplied removal example applies only to an existing Claude Code registration named todoglow-mcp; it does not remove the differently named install example. Confirm the actual host entry before use.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide · Review before use
```
claude mcp remove todoglow-mcp
```

Official Documentation & Sources

What it does

See what each of your coding agents is working on, and read or advance your todos. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Capability: Productivity & Collaboration
Resource type: MCP Server
Best fit: Track coding-agent progress and advance shared task items.

Representative uses

Inspect agent work and to-dos
Advance todo status

Limitations

Workspace sharing, auth and precise mutation scope not verified

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: Not documented in the reviewed sources
Data handling: Not documented in the reviewed sources
Cost: Not documented in the reviewed sources
Risk and cautions: Potential high-impact side effects: Advance task statuses (per source description).

Access scope and cautions

Write actions: Advance task statuses (per source description)
Sensitive access: Task/project metadata
Risk level: moderate

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: Inspect agent work and to-dos; Advance todo status.

Can it modify data or perform write operations?

Documented write actions include: Advance task statuses (per source description).

What data-handling boundary should I consider?

Recorded sensitive-access context: Task/project metadata.

What limitations and risks should I check before use?

Potential high-impact side effects: Advance task statuses (per source description). Workspace sharing, auth and precise mutation scope not verified. 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.