Connect Claude, ChatGPT, Cycls or any MCP client, and what an agent may and may not do in your name.
Hyz MCP lets an AI agent — Claude, ChatGPT, Cycls, or any client that speaks the Model Context Protocol — work inside Haiyz as you. It signs in as you, sees what you may see, does only what you may do, and everything it does is in your audit trail under the agent's name.
Add https://mcp.haiyz.net/mcp as an MCP server in your agent's host. The host discovers Hyz ID,
sends you to sign in (the same sign-in as the Portal), and shows a consent screen naming what the
agent will be allowed to do. Approve it and the agent holds a short-lived token for this server
and nothing else — a token for the Portal does not work here, and this token does not work
anywhere but here.
Only the agents Haiyz has registered can connect. The first release registers three: Claude, ChatGPT and Cycls. There is no self-registration.
An agent asks for scopes, and you approve them. Four exist:
| Scope | Lets the agent |
|---|---|
haiyz.read |
search what you may open; read a service's fields and rows; list a data room's services; follow a job |
haiyz.analysis.run |
run buffer, intersect and spatial join over your services, and publish a result as a service |
haiyz.maps.write |
create a map, add a service to it as a live layer, style a layer |
haiyz.dashboards.write |
create a dashboard and add a map, a chart or an indicator to it |
An agent can create and read. It can never delete anything, share or grant access, invite people, transfer ownership, administer your organization, buy anything, or change your account — whatever scope it holds. And it can never do more than you: a person who may not publish in the Portal cannot publish through an agent.
Every tool takes and returns a service — a Hyz Layer online — or a data item that has one. Nothing goes in or out as a file. When an agent runs an analysis, the result becomes a private data item in your library, exactly as if you had saved it from the Workspace; the agent follows it along the data path (draft → file → online) and publishes it as a service when it is online. That service can then go on a map, and that map on a dashboard.
Runs spend your own tool allowance, and each result tells the agent how many runs are left, so an agent does not keep trying once you are out. Rows come back at most 200 at a time, without geometry unless asked. A refusal reaches the agent with the same code and reason the Portal would show you.
Revoke the agent's access from your account's sessions, or ask Haiyz to disable the agent for everyone. Haiyz can also switch the whole surface off at once, without a deploy.
Hyz MCP is for agents. A system of your own that calls Haiyz uses the Hyz API with an API application and key from the Console.