In development Server scaffold exists. Being re-aimed at stamps, tool sets and profiles — the things Revu's own MCP does not cover.
Role
Read and write Bluebeam Revu's own files — Tool Chest sets, stamps, profiles — and drive Revu from an agent, so a Revu user can adopt MarkupClaw without abandoning their setup.
Tool call → a Revu file (.btx / .bpx / stamp PDF) or a Revu action
Read and write Bluebeam Revu's own files — Tool Chest sets, stamps, profiles — and drive Revu from an agent, so a Revu user can adopt MarkupClaw without abandoning their setup.
Tool call → a Revu file (.btx / .bpx / stamp PDF) or a Revu action
How it connects to MarkupClaw
- MarkupClaw already imports Revu .btx tool sets and reads and writes .mkup and XFDF.
- The Seal Maker will export a Revu-ready stamp PDF with dynamic fields, so one seal serves both programs.
What we are working on
- A setup app: your seal, your firm's tool sets, your profile, deployed to a new Revu seat with one command.
- A .btx exporter (the inverse of the importer) and a .bpx profile generator.
- Studio session and file automation for Core and Complete seats through Bluebeam's Developer Portal.
What it is not
Not a replacement for Bluebeam Max's built-in MCP. Bluebeam sells that; this covers the tiers and the files it does not.
Not a replacement for Bluebeam Max's built-in MCP. Bluebeam sells that; this covers the tiers and the files it does not.