ZAUBERPeople

Authorized automation

Connect as an agent.
Act as a human.

Zauber People exposes one authenticated MCP server and REST API. Registration identifies an agent but grants no data access. An agent never receives broader access than the teammate who authorizes it.

Open llms.txt Human sign-in
Discovery endpoints
Public integration metadata only; people data always requires authorization.
MCP serverStreamable HTTP for clients that understand MCP discovery./mcpProtected resource metadataMachine-readable resource and scope metadata./.well-known/oauth-protected-resource/mcpAuthorization server metadataOAuth endpoints supported by Zauber People./.well-known/oauth-authorization-server/api/authAgent contextA concise plain-text description for an agent context window./llms.txt
Connect from scratch
An unknown agent cannot register itself. It must ask its human for a five-minute, single-use enrollment code.

1. Instruct the humanAsk them to open people.gozauber.com/settings/agents and sign in with their Zauber account.

2. Receive one codeThe human creates a code and pastes it into the agent. Once admitted, the attempt consumes that code before client metadata is validated.

3. Request permissionRegistration grants no HR access. Open the normal OAuth authorization page to request the scopes the client is allowed to use.

Create an enrollment code
Discover
Read this page or llms.txt, then ask a Zauber teammate for a one-time enrollment code.
Authorize
A teammate signs in with Google and approves requested scopes.
Act with parity
Read and write tools reuse the same permissions, versions and audit trail as the web app.
AI-first capability parity
Anything a teammate can do to HRMS business data in the web app is available to an authorized MCP agent through the same application service.

Least privilegehrms:read exposes reads. A newly registered client may request hrms:write directly, but write tools appear only after separate teammate consent.

Human authorityThe teammate's current role still controls every record and field the agent can read or change.

Safe changesUpdates use expected versions and append audited revisions attributed to both the human and agent.

Keep a trusted agent connected
Access tokens expire after 15 minutes. A persistent client does not need to reconnect on a timer: it can renew shortly before its next request.

1. Register explicitlyInclude both authorization_code and refresh_token grants.

2. Ask for consentRequest hrms:read offline_access and, when needed, hrms:write. Registration itself grants nothing.

3. Rotate safelyStore the returned refresh token securely and replace it after each successful refresh.