Your own AI assistant, connected to every module.
Connect Claude, ChatGPT, Cursor, n8n — or anything that speaks the open Model Context Protocol — directly to your hejGuide account. The AI drafts. You publish. Included on Starter and Pro.
Built so you stay the host
Four design decisions you can quote back to a guest who asks how this works.
Bring your own AI
MCP is an open standard. Claude, ChatGPT, Cursor, n8n — connect the assistant you already use. No vendor lock.
You approve every module
OAuth 2.1 with per-scope consent. The AI sees only the modules you grant — reservations, guidebook, places, translations, reports — and nothing else.
Drafts, not sends
New pages, places, translations, message replies and review replies always land as drafts in your dashboard with an AI badge. You click Publish.
Guest data is masked
Guest names are masked by default. Unmasks are capped at 50/day per account, require a reason, and are audit-logged for GDPR.
What you can ask
A few examples from real host workflows. The AI runs the tool; the result waits for your click.
“Translate my full guidebook into German and Italian. Keep the WiFi instructions exactly as-is.”
What happens: Two new translations land as pending updates. Open each, review, accept.
“Summarise this month’s reviews across Airbnb and Booking.com. Which complaints come back more than once?”
What happens: A grouped summary in chat — no PII, no publishing, just analysis.
“A guest is asking about late check-in. Draft a friendly reply in their tone of voice that confirms 22:00 is fine.”
What happens: A draft reply appears in the thread with an ‘AI suggestion’ tag. You send when you’re happy.
“Add three good breakfast spots within a 10-minute walk of the cabin. Include hours and a one-line description each.”
What happens: Three draft places appear in /local-guide with the wand-icon badge. You publish what you like.
“What does this weekend’s revenue look like across all listings, broken down by channel?”
What happens: A clean number in chat. No dashboard click-through needed.
“Open a housekeeping issue for the cabin: hot water tap leaking in the kitchen, priority high.”
What happens: Task created in hejGuide with the right listing and priority — visible to your cleaner immediately.
How to connect
Four steps. You stay in your own AI app the whole time.
Open your AI client
In Claude Desktop, ChatGPT, Cursor, or your n8n flow, add a new MCP server.
Point it at hejGuide
Use the URL https://mcp.hejguide.com/mcp — your client handles the OAuth handshake.
Approve the scopes
hejGuide shows a consent screen. Tick only the modules you want the AI to touch.
Ask away
Your AI assistant can now talk to your account. Anything it writes shows up as a draft in your dashboard.
The boring details (that matter)
Built on open standards. Audited per call. Revocable in one click.
Open standard
The AI Connection is an MCP (Model Context Protocol) server. MCP is an open Anthropic-stewarded standard adopted by every major AI vendor. You are not locked into one provider.
OAuth 2.1 with PKCE
Authentication uses OAuth 2.1 with Dynamic Client Registration, PKCE, and per-scope consent. Tokens are HMAC-hashed, session-bound, and revocable from your account settings at any time.
Audit-logged for GDPR
Every AI call is logged. Guest data is masked by default; unmasks are budgeted (50/day per account), require a written reason, and are retained for 12 months for GDPR traceability.
FAQ
What is the AI Connection?
Which AI assistants does it work with?
How is this different from "AI features" baked into other PMSes?
Does the AI publish things automatically?
Is my guest data safe?
What does "beta" mean here?
Does it cost extra?
Where do I read the technical docs?
Try the AI Connection (beta)
Included on Starter and Pro. 14-day free trial. No credit card required.
Beta · included on Starter and Pro · review before publish