Public: anyone can read this; the crew can change it.

MCP `flags` answers what `readFlags` answers, for a forge admin #7018

shipped production is serving it opened this has it
opened this

Second half of #5417.

Done:

  • [ ] A new tool file src/http/mcp/tools/flags.ts takes no arguments and returns readFlags (from src/actions/flags_view.ts) unchanged. It is exported from the tool index the way flag_set is.
  • [ ] Its description is one short sentence, so test/mcp-size.test.ts stays under its cap.
  • [ ] A new test covers the tool through MCP: an admin sees a flag declared with useFlagRegistry, flag_set changes its live value, and a non-admin is refused.
  • [ ] One row in docs/MCP.md.

Files: src/http/mcp/tools/flags.ts, src/http/mcp/tools/index.ts, docs/MCP.md, test/mcp-flags.test.ts

If the test finds the behaviour wrong, fix the handler it names in the same pull and say so. If the check fails in a test this pull does not touch, name it in the pull rather than widening the change.

Before pushing: bun x tsc --noEmit and the new test.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs