MCP.Market

todoglow MCP server

by devglow.app·app.devglow/todoglow·v1.1.2

See what each of your coding agents is working on, and read or advance your todos.

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

0 stars68 downloads/wk

Reviews

Write one

Nobody has reviewed todoglow yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

todoglow tools (8, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • advance_todo

    Advance a todo's status: pending → in_progress → completed. Use this when a todo is started or finished.

  • get_active_todo

    Get the currently active (in_progress) todo — the one the user is focused on right now.

  • get_threads

    List all agent threads in todoglow. Shows background work status from AI agents.

  • list_receipt_todos

    List completed todos for a month as they appear in todoglow's receipt view,

  • list_todos

    List all active todos in todoglow. Returns id, text, status, and timing info.

  • set_receipt_titles

    Set the receipt display title for one or more todos, in a single batch.

  • set_topic

    Add a todo to the user's todoglow app. Only use this when the user explicitly asks to add a todo (e.g. 'todo 추가해줘', 'add this to my todos'). Do NOT call this automatically at conversation start — use update_thread instead. If called again in the same session with a pending todo, it will UPDATE the text instead of creating a new one.

  • update_threadwrite action

    Register and update your work status in todoglow's AGENTS section. Call this at the START of every conversation with status 'working' and a short task description. Update status as work progresses (working → done/failed). Creates a new thread or updates an existing one by name.

Public scan report

scanner v0.1.10 · 2026-11-04 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 27 days ago15/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace7/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How todoglow compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Tools
8
the typical server has 7
Tools that change things
13%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
68
more than 53% of 12,191 servers with a package

What its tools let an agent do: 5 read · 3 change

Install todoglow in Claude Code, Cursor or VS Code

Runs npx -y todoglow-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add todoglow -- npx -y todoglow-mcp
Add to Cursor

What the publisher says

From the todoglow repository's README, as published. We do not edit it. Read it on GitHub

TodoGlow Releases

MacOS app releases for TodoGlow.

Nothing above is checked by us. What we check is on the safety report.

todoglow: common questions

Is todoglow MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the todoglow safety report
How do I install todoglow?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does todoglow need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is todoglow maintained?
The last commit was 27 days ago (2026-10-08). The latest release is v1.1.2.
How does todoglow compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 13% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from devglow.app →