MCP

Livy MCP is the runtime surface agents use for protected actions.

The endpoint is project-scoped and authenticated with a runtime API key. It is the path that creates Livy requests, policy decisions, approval nonces, execution state, and receipts.

Endpoint

Use the endpoint shown in MCP Setup:

<backend-base-url>/api/v1/tenants/<tenant-id>/projects/<project-id>/mcp?integration_id=<integration-id>

Send the runtime key as:

Authorization: Bearer $LIVY_API_KEY

Tool Order

Protected actions should use this order:

livy_list_actions
livy_prepare_action
livy_authorize_action
livy_execute_approved_action
livy_get_request_status

Tool Roles

• livy_list_actions returns the actions the runtime key can request.
• livy_prepare_action creates the canonical request payload.
• livy_authorize_action evaluates wallet profile and guardrails.
• livy_execute_approved_action executes only an approved exact bundle when execution is enabled.
• livy_get_request_status returns the request, decision, execution, and receipt state.

Direct Sends

Direct wallet sends are unprotected.

They do not create:

• a Livy request
• a guardrail decision
• an approval nonce
• an exact-bundle execution check
• a Livy receipt

If the action needs Livy protection, route it through MCP.

Read Next

• Agent Wallet
• Guardrails
• Skills