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. Six 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; read a map, a dashboard and what each widget reads, and a campaign |
haiyz.analysis.run |
run buffer, intersect and spatial join over your services, publish a result as a service, and ask Hyz Insight to explain a dashboard widget (one of your AI requests) |
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 |
haiyz.field.write |
create a field campaign and its form as a draft you launch yourself, and an empty data item made from a form for it to fill |
haiyz.data.link |
link a data item from a public external service, kept private to you |
An agent can create and read. It can never delete anything, share or grant access, invite people, transfer ownership, administer your enterprise, 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.
A platform that hosts agents adds Hyz MCP once, for all its users. Haiyz registers the platform first — send us the callback (redirect) URL your OAuth flow returns to — and you receive a client id. Then:
| MCP server | https://mcp.haiyz.net/mcp — Streamable HTTP, stateless, POST only |
| Client | public: the client id, no secret |
| Flow | OAuth 2.1 authorization code with PKCE S256 |
| Resource | send resource=https://mcp.haiyz.net/mcp on the authorize and token requests (RFC 8707); without it the token cannot be used here |
| Discovery | https://mcp.haiyz.net/.well-known/oauth-protected-resource/mcp names the authorization server; its metadata is at https://haiyz.net/api/auth/id/.well-known/openid-configuration |
| Scopes | haiyz.read haiyz.analysis.run haiyz.maps.write haiyz.dashboards.write, plus offline_access for a refresh token |
An unauthenticated call to the server answers 401 with a WWW-Authenticate header pointing at
the discovery document, so a client that follows the MCP authorization specification finds
everything on its own. Access tokens last 15 minutes; refresh tokens 30 days. Every person who
connects sees the consent screen for your platform, by name.
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.
On a Haiyz Enclave, Hyz MCP runs on your host: the server is https://mcp.<your domain>/mcp, Hyz ID on the same host signs in your people and issues the token, and nothing reaches Haiyz Cloud. Your operator registers each agent host (scripts/mcp-client.sh add) instead of Haiyz, and the discovery addresses above read with your domain in place of haiyz.net.
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.