---
name: bluebeam-markup-review
description: Work with markups in Bluebeam Revu through its official MCP server (Bluebeam Max plan, Revu 21.9+, desktop with Claude, ChatGPT, GitHub Copilot CLI or AnythingLLM) - list and summarise markups, filter by author, status or layer, set review states, export/import custom columns, search text, stamp and bookmark - for design reviews, punch lists and RFI preparation. Use when the user works in Bluebeam/Revu and asks to summarise comments, track review status, "resumir los comentarios del plano", prepare a review log, or connect Bluebeam to the AI.
---

# Bluebeam Revu markups through MCP

## Requires (check first)
- Bluebeam Max plan, Revu 21.9 or later on desktop (Revu Offline licences and web/mobile do not support MCP).
- An admin enabled it: Revu > Preferences > Admin > MCP, client selected. The AI desktop app shows Bluebeam as a connector.
- The PDF to work on is the **active document** in the primary Revu window. Studio Projects are reached through `list_studio_projects`, `studio_project_search` and `open_file`.
- Some tools need Revu 21.10 or 21.11 (`add_markup`, `delete_markup`, `search`, custom columns, links). If a tool is missing, ask the user to update Revu.

## Useful tools (names as published by Bluebeam)
- Read: `get_page_count`, `get_page_information`, `save_as_text`, `list_markups_in_pdf`, `get_markup_state`, `list_state_models_in_pdf`, `get_bookmarks`, `list_links_in_PDF`, `search`.
- Write (ask first): `set_markup_state`, `set_markup_property`, `add_markup`, `delete_markup`, `stamp`, `create_bookmarks`, `set_page_labels`, `set_page_scale`, `redact`, `import_custom_columns`.
- Export: `export_custom_columns`, `export_state_models`, `create_markup_thumbnail`.

## Procedure (design review / comment log)
1. `list_markups_in_pdf`; build a table: page/sheet, author, subject, comment, status, layer, date.
2. Summarise: totals by author, discipline/layer and status; comments without status; duplicates on the same location.
3. Draft responses or RFIs for comments that need a designer decision (hand off to `rfi-writer`).
4. Only after the user approves the list: set review states (`set_markup_state`) in small batches and read them back.
5. Export the log (custom columns or CSV) for the meeting.

## Limits to tell the user
- Visual searches (e.g. counting door symbols) do not work through MCP; use text search or Revu's own Visual Search.
- Flattened markups are not recognised; scanned text needs OCR first; secured or certified PDFs can block tasks.
- Prompts, extracted text and markup metadata go to the AI provider; linework does not. Respect the project's confidentiality rules.

## Never
- Never delete, flatten or redact without an explicit confirmation of the exact markups/pages.
- Never change a markup's status on behalf of a reviewer without their approval.