The GTM MCP Directory
Directory / Updates
The public feed

What changed.

These pages are the daily and weekly reports already sitting in directory/digests/. The rail mails them to Andrew and the newsletter lifts lines from them. This bake turns each file that exists into a public page. A date with no file has no page.

1,252
entries in this bake, 2026-09-27
201
official MCP servers, 2026-09-27
10
daily digest files on disk
2
weekly digest files on disk

The two gold tiles are the current directory.json counts, dated 2026-09-27. They are not a digest delta. Numbers inside a digest page belong to that file's own build date.

Daily files are missing for 2026-09-16, 2026-09-18, 2026-09-19, 2026-09-20, 2026-09-21, 2026-09-22, 2026-09-23, 2026-09-24, 2026-09-25. Those dates have no page. Latest daily file: 2026-09-26. Latest weekly file: 2026-09-18. A later date is unpublished until digest.py writes the file. This bake does not invent one.

Weekly

Friday roll-ups.

2 weekly files on disk.

  • Build date 2026-09-18. Deltas are against the previous digest of 2026-09-17. Every number is a measurement on its date; none-found and unresolved are probe results, not absence.
    GTM tools in the directory: 1,252 no change; with an official MCP server: 201 no change; servers that answer a live handshake: 27 no change; individual MCP tools catalogued (gateways excluded): 3,056 +34; tools with an official CLI: 137 +1

    Source file DIGEST_2026-09-18_weekly.md.

  • Build date 2026-09-11. Deltas are against the previous digest of 2026-09-11. Every number is a measurement on its date; none-found and unresolved are probe results, not absence.
    GTM tools in the directory: 336 no change; with an official MCP server: 200 no change; servers that answer a live handshake: 26 no change; individual MCP tools catalogued (gateways excluded): 2,516 -7; tools with an official CLI: 55 +1

    Source file DIGEST_2026-09-11_weekly.md.

Daily

Day-by-day files.

10 daily files on disk.

How a file becomes a page: directory/UPDATES_FEED.md. digest.py still writes the files. Moving that job off the EC2 rail onto Powerhouse is not part of this bake.