Hapee MCP connector

Use Hapee from your AI assistant. You sign in with your own user and the assistant works with exactly your permissions: it sees what you see and changes only what you can change.

What it is

The connector is an MCP server (Model Context Protocol, the open standard AI assistants use to connect to external tools). Once you add it to a compatible assistant —Claude, ChatGPT, Grok Bot or any other that accepts remote MCP connectors— you can ask it in plain language things like “show me this week's open deals,” “create a contact with this data” or “book an appointment for tomorrow at 10.”

The connector does not store your Hapee data: each tool is a call to the Hapee API v1 made with your own session. There are no shared keys or secret URLs: each person connects with their own Hapee user.

The connector URL

https://mcp.hapee.ai/mcp

It is the only address you need. It carries no credential: sign-in happens afterwards, on a Hapee screen.

Connect it to your assistant

Each assistant puts the option in a different place in its settings, and those menus change often, so here are the generic steps. The procedure is the same in all of them:

1. In your assistant's settings, add a custom (or remote) MCP connector with the URL above. If it asks for a name, use “Hapee.”
2. If it asks for the authentication type, choose OAuth. You don't need to enter any client ID or secret: the assistant registers itself.
3. The assistant opens a Hapee window. Sign in with your user and approve the connection (see the next section).
4. You return to the assistant with the connector active. Ask it, for example, “who am I in Hapee?” to check which user and subaccount you are connected as.

• Claude: add a custom connector with the connector URL.
• ChatGPT: add a remote MCP connector with the connector URL.
• Grok Bot: add a remote MCP connector with the connector URL.

If your organization manages connectors centrally, an administrator may need to add it first.

Sign-in and consent

The window the assistant opens is the one at beta.hapee.ai, the same one you use to enter Hapee every day. You sign in there as usual:

• with your email and password, plus your two-step verification if you have it enabled, or
• with Google, if that is how you normally sign in.

The assistant never sees your password: it only receives a temporary permission that Hapee issues when you approve it. After signing in, the consent screen appears, showing which application is requesting access, which address it will send you back to, which account and agency you are connecting with, and what it will be able to do. There you can remove the write permission if you want the assistant to only be able to read.

What it can do

The connection requests these permissions (scopes):

Permissions only subtract, never add. Above the scopes, your real Hapee user rules: your role, your permission profile, the active modules and, if your profile is “assigned only,” just what is assigned to you. If your administrator changes your profile's permissions, they apply from the next call; if they assign you another role or profile, the connection is disconnected and you have to connect again. No connection can do anything you couldn't do from the screen.

The list of tools the assistant sees is also built for you: only the ones your permissions allow appear, and write tools only if you approved hapee:write.

Agencies and subaccounts

The connector works on one subaccount at a time: the business you operate in Hapee.

• Subaccount user (customer): the connection is tied to your subaccount. If you have access to more than one, you choose which on the consent screen; to change it, connect again.
• Agency team (owner, administrator or team member): you choose the subaccount in each conversation with the select_subaccount tool. With no arguments it lists the subaccounts you can see; with an id it pins that subaccount for the rest of the conversation. It only accepts subaccounts your user can already see in Hapee. The agency's internal administration (subaccounts, team, internal tasks) is not in this connector.
• Platform administration access does not extend to the connector.

Tools

The connector offers 240 tools on top of the Hapee API: 85 read-only and 155 that modify data. How many you see depends on your permissions. Their names are in English, as the assistant-directory standard requires; your assistant replies and writes content in your language.

Tools that modify data

Each tool declares its nature with the standard MCP annotations, so your assistant can ask for your confirmation before running something:

• Read-only (readOnlyHint: true): the 85 read tools. They change nothing (two of them, validating a workflow and counting an audience, use POST but save nothing).
• Create or add (readOnlyHint: false, destructiveHint: false): 48 tools, such as creating a note, a task, or a landing page or campaign draft.
• Edit, delete or act outward (readOnlyHint: false, destructiveHint: true): 107 tools that change or remove something that already exists, publish or send.
• Reach outside Hapee (openWorldHint: true): 38 of them, such as sending a message, a quote or an email campaign, publishing a page or pointing a domain. The connector tells your assistant to ask for your confirmation before using them.

How long the connection lasts

• The access permission the assistant uses lasts 1 hour.
• The assistant renews it on its own with a renewal permission that lasts 30 days from its last use and changes on every renewal (the previous one stops working). If someone tried to reuse one that was already used, Hapee cuts the entire connection.
• No matter what, 90 days after you approved it the connection expires and you have to sign in again.

Disconnecting it

You have several ways to cut off access:

• From Hapee: in your Profile, the “Connected AI assistants” section lists every assistant you connected, with its subaccount and last use; “Disconnect” cuts its access instantly.
• From your assistant: remove or disconnect the connector in its settings. If the assistant notifies Hapee when disconnecting, the connection is revoked right away; if not, it simply stops being used and expires on its own within the timeframes above.
• Changing your password or your two-step verification: automatically disconnects all your assistant connections.
• Changes to your user: if your administrator changes your role, permission profile, agency or subaccount, or deactivates your user, your connections disconnect on their own.
• The agency owner can revoke any connection of their agency from the Hapee API keys screen: they appear as “OAuth: <application name>.”
• If you need help cutting off access, write to us at info@hapee.ai.

Limits

• Each connection has the same limit as any API credential: 100 calls per minute. If your assistant exceeds it, it gets a temporary error and just needs to wait a few seconds.
• Automatic application registration is limited to 20 registrations per hour from the same IP address.
• Lists return up to 100 items per page, just like the API.

Technical details

For anyone integrating their own MCP client or reviewing the connector:

• Transport: MCP over Streamable HTTP at the connector URL.
• Discovery: a request without a token receives 401 with WWW-Authenticate: Bearer resource_metadata=…, which points to /.well-known/oauth-protected-resource on the same host (RFC 9728).
• Authorization server: https://beta.hapee.ai, with its metadata at /.well-known/oauth-authorization-server (RFC 8414).
• OAuth 2.1: dynamic registration of public clients (RFC 7591), PKCE required with S256 only, renewal-token rotation with reuse detection, revocation (RFC 7009) and resource-bound audience (RFC 8707). Redirect URIs must be https, or http only to the local machine.
• Sessions: each MCP session is tied to the person who opened it; a token from another person in the same session is rejected.

Privacy

The connector only accesses what your own permissions let you see, and the MCP server does not store your Hapee data: what it reads passes to your assistant and is subject to that assistant's privacy policy. The detail of what is stored, where and for how long is in the “MCP connector for AI assistants” section of our privacy policy.