The Model Context Protocol is becoming a common way for AI clients to work with the systems a business relies on. Cadae offers an MCP server beside its REST API, so an AI client can read your hotels within the access you already have.
Two public interfaces share one set of permissions:
- REST API at
https://api.cadae.ai/v1, described by an OpenAPI document - MCP server at
https://api.cadae.ai/mcp, with tools filtered by the scopes of your credential
What that means in practice
Ask Claude: "Which hotels do I manage?" It calls hotel_list with your OAuth
token and answers with your actual hotels, in your language. Ask it to invite
an Administrator for a Munich hotel: invites_create with a per-hotel grant,
and the invitation email arrives in German.
Permissions are the whole point. Portfolio tokens suit automation. Personal tokens are limited to your own access. OAuth consent limits a client to what you can actually do. A tool that changes or removes something asks for a confirmation before it runs.
Read the MCP docs to connect your client.