prom CLI & MCP bridge
Live product context inside a coding agent
A published npm package that links a customer's repository to a PROM product, keeps an ambient context block in sync inside their agent instructions file, and proxies PROM's MCP server over stdio — so a coding agent can ask what to build next, read acceptance criteria, and report work back, without a human relaying any of it.
- Role
- Designer & Author
- Team
- Built as part of PROM
- Timeline
- 2026
- Status
- Shipped
The idea
Coding agents are excellent at writing code and blind to why it is being written. The requirement, the acceptance criteria and the decision that ruled out the obvious approach all live in a tool the agent cannot see.
The bridge closes that loop. The agent asks PROM what to work on, gets the task with its criteria and blockers, and reports status back when it finishes — with destructive actions escalated to a human rather than executed.
The work, specifically
- 01
Exposes PROM's task, spec and decision surface to any MCP-capable agent as first-class tools.
- 02
Generates and refreshes a delimited context block in the repo's agent instructions, so edits outside the markers survive regeneration.
- 03
Degrades gracefully before publication — writes an absolute path to a local build so the generated config works either way.
- 04
Refuses destructive operations by design: an agent asking to delete raises a proposal for a human instead of executing.
What it is made of
- CLI
- TypeScriptNode 20+tsxstdio transport
- Protocol
- MCPJSON-RPCSession tokens
- Server
- NestJS MCP moduleScoped agent tokensWrite proposals