Integrations
API · Connected
Claude
Claude and other AI agents read the governed Master Profile over Casa Layer's MCP server, acting on complete guest context in real time. Casa serves the profile; the agent runs on it.
The connection
- Served through
- MCP server
- Direction
- Casa Layer serves the Master Profile to Claude. The record flows outwards: Claude is not a source we read guest data from.
- Status
- Connected
- Website
- claude.com
What this takes from you
- Work on your side
- Nothing to build per agent. Claude reads the same record through the MCP server as every other consumer, so there is no bespoke integration to commission.
- Cost to you
- Serving the record to an agent is part of the platform licence, not a separate integration fee. What you pay Claude for its own usage is between you and them.
- Time to first answer
- Once your Master Profile is live, pointing an agent at it is configuration rather than a build.
- What the agent cannot read
- An agent can only read what the record holds, and the record never holds:
- Payment card numbers, CVV codes, or anything else in PCI DSS scope
- Rate negotiation, contract, and commercial terms
- Staff, payroll, and HR records
- Anything outside the read scope you approve before we connect
See Casa Layer in practice
A 20-minute demo covers how Casa Layer connects to Claude and the rest of your stack, resolves one Master Profile across them, and serves it to any agent through the MCP server and REST API.
Book a 20-minute demo