Connecting the MCP Servers
Both servers live under the ZenSpace API domain. Add them as custom connectors in your chat agent, then confirm the tools are live before running any prompt.
| Server | Connector URL | Auth |
|---|---|---|
| ZenCore Booking | https://api-zencore.zenspace.io/api/v1/mcp/zencore-public | None |
| ZenCore Admin | https://api-zencore.zenspace.io/api/v1/mcp/zencore | OAuth · org access |
In Claude
-
Open Settings → Connectors and choose Add custom connector.
-
Paste the connector URL (use the Admin URL for operator work, the Booking URL for the guest flow).
-
For the Admin server, complete the OAuth sign-in, then select the organization you have access to. The MCP then works according to your role in that org. The Booking server needs no sign-in.
-
Confirm the connector shows as connected and its tools appear in the tool list.
In ChatGPT
-
Open the connector / custom-integration settings and add a new MCP server.
-
Paste the same connector URL; authorize the Admin server and select your organization when prompted.
-
Confirm the tools load before running a prompt.
Important — reconnect after any change, and watch tool names
Reconnect, don’t just refresh — a chat agent caches the tool list at connect time. After any tool update, do a full disconnect then reconnect so you’re testing the current tools.
Confirm tools are callable — some clients silently drop tools they can’t parse. If a tool appears in the list but never fires, reconnect and re-check before assuming the server is at fault.
Admin MCP is org-scoped
The Admin connector needs a signed-in account with access to an organization. When you connect it, choose the organization you have access to — every tool then runs against that org, with whatever permissions your role allows. For this guide, select Grand Meridian Hotel.
Tip — keep two connectors side by side
Connect the Booking server and the Admin server at the same time. The guest flow and the operator flows then run in one place, exactly as they do in a real deployment.
VISITOR SIDE