D3x console
Stops at the answer.
Output
Visual exploration and configuration
- Team workflows and admin setup
- Best for operators configuring agents
D3X MCP
Run your entire operation from any LLM — or wire in your stack.
CIOs and technology leaders orchestrate D3x from Claude, other MCP-compatible models, or third-party operators and internal systems — pull production reports, trigger actions, and converse with D3x directly. No dashboard required.
LLM & clients
Claude · GPT · custom apps
D3x MCP
Model Context Protocol
D3x + your stack
PMS · ops · BI · ITSM
Any MCP-compatible client or operator connects to D3x through MCP
WHAT IS MCP
An open protocol — not tied to one model or vendor.
Model Context Protocol is an open standard for connecting AI applications and automation to real tools and data. D3x exposes your agent runtime, integrations, and operational data through a secure MCP server — whichever LLM or operator your organisation standardises on can become a control plane for hospitality operations.
WHO CONNECTS
Any LLM, client, or third-party operator.
D3x MCP is client-agnostic. Connect the assistant your teams already use, or wire operational and analytics systems that need live access to D3x — with the same credentials, policies, and audit trail.
LLMs & AI clients
- Claude Desktop, Cowork, and Claude API
- Any MCP-compatible host or custom copilot
- Internal AI workspaces your group already deploys
Third-party operators & systems
- BI, reporting, and portfolio analytics tools
- Workflow automation and orchestration platforms
- ITSM, internal ops consoles, and custom middleware
FOR CIOs
Your operations desk, wherever you work.
Technology leaders live in AI assistants, automation layers, and internal tools — not another vendor console. D3x MCP meets you there: the same production agents, Skills Engine, and audit trails, whether the call comes from an LLM chat or a connected operator.
01
Pull reports on demand
Autonomous resolution rates, CSAT, channel mix, escalation volume, and property-level breakdowns — generated from live production data, not exports you schedule.
02
Run operations without the UI
Ask D3x to inspect queues, review open tickets, or summarise what happened on a guest thread — the runtime executes with the same guardrails as messaging and voice.
03
Converse with D3x directly
Multi-turn dialogue with full context: clarify policies, explore edge cases, and get explainable answers backed by decision logs and integration state.
04
Wire third-party operators
Connect BI tools, automation platforms, or internal systems that need programmatic access — scoped credentials and tool policies per integration, not open API keys.
05
Same governance as the platform
Role-based access, confidence thresholds, human-in-the-loop rules, and immutable audit trails apply to every MCP call — from any LLM or operator, not a shadow IT channel.
HOW IT WORKS
Connect once. Operate from any client.
01
Connect your LLM or operator
Add the D3x MCP server to Claude, another MCP-compatible client, or your third-party system. Authenticate with organisation-scoped D3x credentials — SSO, IP allowlists, and role policies apply.
02
Ask in natural language or invoke tools
Request reports, operational summaries, or specific actions across properties. The client calls D3x tools with your portfolio context and permissions — conversational or programmatic.
03
D3x executes with full audit
Agents run against your live PMS and ops stack. Every tool call, outcome, and confidence score is logged — identical to actions initiated from the platform.
SETUP
Add D3x MCP to your client or operator.
Your team receives an MCP endpoint and credentials scoped to your hotel group. Configure once per client or system — then every authorised user or integration operates within the same policies as the D3x console.
Example — Claude Desktop
{"mcpServers": {"d3x": {"url": "https://mcp.d3x.ai/sse","headers": { "Authorization": "Bearer <your-org-token>" }}}}
Enterprise deployments: contact D3x for SSO, IP allowlists, and per-role tool scopes.
EXAMPLE PROMPTS
What CIOs ask in production.
Natural language replaces clicking through dashboards. Examples from groups running D3x in production:
Reports
“Pull last week's autonomous resolution rate by property and channel.”
Operations
“Show open housekeeping tickets for Berlin properties and escalate anything older than 4 hours.”
Guest context
“Summarise guest conversations for room 512 — what was promised and what executed in PMS?”
Audit
“Export the decision log for yesterday's WhatsApp escalations with confidence scores.”
GOVERNANCE
Production controls, not a bypass.
MCP is an interface to the same runtime — not a separate integration with weaker rules.
- Organisation-scoped credentials with role-based tool access
- Confidence thresholds and escalation policies enforced on every action
- Immutable decision logs and data retention aligned with GDPR
- Optional human-in-the-loop for high-risk operations
- Same subprocessor and security posture as the D3x platform
WHY MCP
Dashboard when you need it. MCP when you don't.
D3x MCP (any client)
Answers, then executes.
Output
Any MCP-compatible LLM or third-party operator
- Natural language or programmatic tool calls
- No separate login for day-to-day leadership
- Full audit trail on every MCP action
TALK TO US
Enable D3x MCP for your group.
30 minutes with the founder — scope, security review, and client options for your stack.