dailypoint brings hotel intelligence to MCP and Zapier

The hotel industry has spent years accumulating guest data in CRM and CDP platforms without that information reaching the systems teams use daily. dailypoint™, the German data management platform for independent hotels and boutique chains, has just taken a concrete step in that direction: it has announced native support for MCP and integration with Zapier, according to Hospitality Net on June 15, 2026.

What dailypoint has actually done

The announcement has two distinct parts:

• Own MCP Server: dailypoint now exposes an MCP server that allows AI assistants, including Claude configured in `claude_desktop_config.json` or via Claude Code, to query guest profiles, stay history, preferences and loyalty segmentation directly during a conversation or automated task. In practice, an agent can ask "what room does guest García prefer when traveling alone?" and receive the answer from dailypoint's CDP without anyone having to manually copy and paste data.

• Zapier Integration: For teams that don't work with LLMs but do use no-code tools, dailypoint adds Zapier connectors that allow you to trigger workflows when a profile is updated, a reservation is confirmed, or a guest reaches a loyalty threshold. Combined with Zapier, automation becomes accessible to revenue managers or marketing leads without REST API access.

Why this matters beyond the hotel sector

From an MCP ecosystem perspective, this case illustrates something we've seen grow strongly in recent months: protocol adoption is not happening only in tech companies, but in verticals with highly specific and regulated data, such as healthcare, finance, or in this case, hospitality.

Guest data in hotels is sensitive—personal preferences, behavioral patterns, spending history—and exposing it via MCP requires providers to carefully design permissions and scope for each tool. The announcement does not specify what authentication and scoping model the dailypoint server uses, which is a relevant question before connecting it to any agent with access to write operations.

For integrators working with Claude Code or any compatible MCP client, the arrival of this type of server means that workflows for assisted check-in, welcome personalization, or VIP guest churn analysis move from multi-sprint projects to configurations that take a few hours, assuming the server documentation is solid.

Who this is useful for

• Hotel operators already using dailypoint as a CDP: can connect their data to internal assistants or Zapier workflows without custom development.
• Hotel automation integrators and agencies: have a new connector to add to their tool catalog for value propositions.
• Developers building agents with Claude Code: if they work in hospitality verticals, this MCP server can save weeks of data engineering work.
• Hotel revenue and marketing teams: the Zapier route lets them automate without depending on the IT department.

A note on the broader context

dailypoint's move is not isolated. Since Anthropic published the open MCP specification, the number of vertical-specific servers has grown steadily. dailypoint's commitment confirms that sector data providers see MCP as a distribution layer rather than point-to-point integrations. If the server is well built and documented, a single integration effort gives them presence in any agent compatible with the protocol.

---

EP: That a hotel CDP bets on MCP instead of building its own proprietary chatbot is a sensible signal; it suggests the protocol is beginning to function as infrastructure rather than as technological novelty. It remains to be seen whether the permissions implementation matches the sensitivity of the data it handles.