Connect Claude or ChatGPT to your rental admin, step by step

What is MCP, in plain language?

MCP is a standard plug between AI assistants and apps — think of it as a USB port for AI. The assistant you already pay for (Claude, ChatGPT, Cursor, or an automation tool like n8n) plugs into your rental admin and can then read your bookings, drafts replies in context, summarise reviews, or add places to your local guide.

Because it’s an open standard stewarded by Anthropic and adopted across the industry, you’re not locked into one AI vendor. Switch assistants tomorrow; the connection works the same.

This is the opposite of “AI features” baked into a PMS: there you use their AI, on their terms. Here you bring your own — the model, the subscription and the chat history stay yours.

What you can actually ask

A few real examples, from analysis to action:

• “Look across my bookings, reviews and messages from the past week — what are the three things I should act on?” → a ranked shortlist in chat; nothing is changed.
• “Summarise this month’s reviews. Which complaints come back more than once?” → grouped summary, no publishing.
• “A guest asks about late check-in — draft a friendly reply confirming 22:00 is fine.” → a draft appears in the message thread with an AI badge; you press send.
• “Add three good breakfast spots within 10 minutes’ walk of the cabin.” → three draft places in your local guide; you publish the ones you like.
• “Open a housekeeping issue: hot water tap leaking, priority high.” → a task is created and visible to your cleaner.

Setup in Claude (Desktop or claude.ai)

1. 1Open Claude’s Settings → Connectors and choose “Add custom connector”.
2. 2Paste the hejGuide endpoint: https://mcp.hejguide.com/mcp
3. 3Claude redirects you to hejGuide to log in. You’ll see a consent screen listing modules (reservations, messages, guidebook, places, reports, …) — tick only what you want the AI to touch.
4. 4Done. Ask Claude something like “what are this week’s check-ins?” to confirm the connection.

Setup in ChatGPT and other clients

ChatGPT supports MCP through its connector/apps settings (availability varies by plan — check OpenAI’s current docs). The flow is the same: add the hejGuide MCP URL, complete the login, approve the scopes.

Cursor and n8n work too: add hejGuide as an MCP server in their settings and you can build host automations that respect exactly the same permissions and draft flow. Step-by-step guides per client live on help.hejguide.com.

The safety model: why this doesn’t run wild

Connecting an AI to real guest data deserves more than a shrug. Four design decisions:

• Drafts, not sends. New pages, places, translations, message replies and review replies always land as drafts with an AI badge in your dashboard. You click Publish. (Single exception: internal team-chat messages send directly — like they do for you.)
• You approve every module. OAuth 2.1 with per-scope consent: the AI sees only what you granted, and you can revoke access in one click from your settings.
• Guest data is masked. Names show as “Anna K.” by default; unmasking is budgeted (50/day), requires a reason, and is logged.
• Everything is audited. Every AI call is logged for 12 months for GDPR traceability.

Frequently asked questions