The Genezio MCP server uses OAuth 2.1 to authenticate an MCP client. The client acts as your Genezio user, with the permissions that you give it on the consent page: Read, Write, or both. When a client connects, Genezio opens the page Connect client to Genezio in your browser. The page shows the name of the client and two permissions: You can clear a permission that the client asks for, but one permission must stay selected. Click Allow access to connect, or Deny to refuse.

What each scope permits

  • A tool that only reads needs mcp:read.
  • A tool that changes data needs mcp:write.
  • A client does not see the tools that its scopes do not permit. If it calls one, Genezio tells it to connect again with the required permission.
  • The scopes do not give access to more brands. The client sees only the brands that your Genezio user can open.
The MCP tools reference gives the scope of each tool.

The audit log

The tool list_audit_log_entries reads the audit log of one account. A scope is not enough for it: only an owner of that account reads the log. A member, a viewer or a custom role gets an error, with the read scope or without it. An entry tells who did what, to which resource, and when. It carries no payload of an operation and no IP address, and a client cannot search the text of an entry. The Audit Logs page of the dashboard continues to give the full entry to an owner. The tool filters on a time window, on one or more actions, on one or more resource types, on the id of one resource, on the full email address of one person, and on one brand. A part of an address matches no entry, thus a client cannot search for the people of the account. Each entry names the brand that the action touched, with the id and the name of that brand. An action of the whole account touches no brand, thus a sign-in, a change of a role and a rotation of an API key each name none. The filter brand_id therefore drops such an entry: the log of a brand answers when a person was last active on that brand, and not when that person signed in. A sign-in reaches an account and not a brand. A read by an MCP client is one entry for the whole session, because one turn of a client calls many tools. That entry names no brand, thus the log of a brand holds the writes of a client and not its reads. The tool list_audit_log_people gives the addresses that the filter takes. It names each person who holds an entry in the log, with the number of entries and the moment of the newest one. It reads the log and no other table: a member who did nothing holds no entry, thus the answer is no list of the members of the account. No tool gives the members of an account. The tool takes one brand as well, thus it names the people who were active on that brand, each with the moment when that person was last active on it. Each read of the log writes its own entry. An owner thus sees on the Audit Logs page that a client read the log, and when.

Token lifetime

The client refreshes the access token by itself. After 30 days with no use, you sign in again.

OAuth endpoints

The client finds these endpoints by itself. You need them only to write your own client. Each path is on the host of the MCP server. The server supports the authorization_code and refresh_token grants, with PKCE (S256). A public client has no client secret.

API keys and the MCP server

An API key of Genezio (gnz-...) works only with the REST API. The MCP server does not accept it. Use OAuth to connect an MCP client.