Skip to main content

diagrid mcpserver access user-identity

Manage the user identity requirement for an MCP server

Description​

Manage whether calls to an MCP server must carry an end user's identity.

An agent normally calls an MCP server as itself, and the server has no way to tell which person the work is being done for. Requiring a user identity changes that: every call must also carry the identity of the person it acts for, and a call without one is refused before it reaches the server.

Turn it on when the server's data or actions belong to individual users rather than to the agent — so the server can apply that person's permissions, and so its audit trail names them.

Requiring an identity is also what causes one to be sent: with no requirement set, no user identity reaches the server at all.

This is separate from how the server authenticates to its own upstream, which is configured on the MCPServer. Turning this on does not change that.

Options​

  -h, --help   help for user-identity

Options inherited from parent commands​

      --api-key string   Diagrid Cloud API key

SEE ALSO​

Last updated on