Why is Bluebeam MCP locked behind Max if Claude is doing the AI?
I was looking into Bluebeam’s new MCP / Claude integration, and maybe I’m missing something, but the pricing feels weird to me.
From what I understand, the AI part is not actually Bluebeam’s AI. You still need Claude / Anthropic. Bluebeam is basically exposing a local MCP server so Claude can interact with Revu, read PDF data, work with markups, change properties, set page labels, etc.
That is useful, but if I’m already paying for Bluebeam and I also need to pay for Claude or deal with Claude’s usage limits, why is the MCP bridge locked behind the expensive Max subscription?
I get charging more for real Bluebeam-built AI features, enterprise admin tools, Studio automation, smart review, batch workflows, etc. That stuff takes real development and support.
But a basic MCP connector feels more like interoperability. It is basically letting the software I already pay for talk to the AI service I also pay for.
To me, the fair model would be:
- Basic MCP access included with Revu
- Advanced automation / Studio / admin / batch tools in Max
- User brings their own Claude account
Otherwise it kind of feels like paying Bluebeam a premium just for permission to use another company’s AI with files already open in Revu.
Not saying MCP is useless. I actually think it could be very useful for estimators: summarizing markups, checking page labels, extracting notes, cleaning up statuses, finding inconsistencies, etc.
I just don’t like the direction where every existing software company adds a connector to Claude/OpenAI and suddenly calls it a premium AI feature.
Curious what other estimators think. Would you pay for Bluebeam Max just to use MCP with Claude, or should this be included in regular Revu?