Skip to main content
A session is a short-lived, revocable credential that lets an MCP client connect as a single tenant user. Instead of handing an agent your workspace API key, you mint a session: it returns an MCP URL plus a bearer token (an nv_sess_… token) that expires and can be revoked at any time. The session’s tool list is the fused native + third-party toolset, filtered by that user’s Account Kit. See Architecture → Sessions.

Tools

ToolTypeDescription
sessions_createCoreMint a TTL-limited MCP session for a user
sessions_listCoreList a user’s sessions and their status
sessions_revokeManagementRevoke a session immediately

Creating a Session

The token travels in the Authorization header — never in the URL. The returned mcp.url + mcp.headers are everything an MCP client needs to connect.
Response:

Parameters

ParamTypeRequiredDefaultDescription
ttl_msnumberNo900000 (15 min)Session lifetime in ms (max 24h)
The MCP connection is bound to the session’s tenant user: multi-tenant tools (connections, vault, logs) default to that user, and execution stays gated by the user’s Account Kit. Revoke a session and the connection is rejected immediately.

Listing & Revoking

A session is active, expired (past its TTL), or revoked.

Error Handling

ErrorCauseRecovery
not_foundInvalid session_id / user_idUse GET .../sessions for valid ids
unauthorizedThe nv_sess_… token is expired or revoked (at connect time)Mint a fresh session
invalid_inputttl_ms out of rangeUse 1ms–24h

Typical Workflow