Expected outcome
Cursor can perform the agreed job in the selected workspace without receiving broader access than it needs.
Tempera is in private preview and provides private APIs across its product areas. Access is arranged through onboarding for an agreed evaluation, with product-specific credentials, endpoints, and environment details supplied directly to your team. API maturity ranges from preview to research, and no shared cross-product endpoint is implied.
Before you start
- A provisioned design-partner workspace
- An approved Cursor use case
- A workspace owner who can review requested permissions
Steps
- 01
Confirm the job and workspace
Write down what Cursor needs to do and which staging workspace contains the permitted data.
- 02
Use the supplied connection details
Use the client registration, sign-in link, or configuration supplied during onboarding. Tempera does not publish a shared endpoint or generic public configuration in this guide.
- 03
Match permissions to this job
Approve only the tool invocation required by the integration task. Trace, dataset, evaluation, and administrator permissions are outside this narrow connection.
- 04
Run the client-specific check
Call one approved read-only discovery tool from the intended project, then verify that no unrelated workspace data appears.
What success looks like
- Cursor shows as connected for the selected workspace.
- The approved permissions match the documented job.
- Cursor can invoke the approved tool in one workspace without separate data or administrator permissions.
If something is blocked
- If the connection is expired or revoked, reconnect the same client instead of creating a broader credential.
- If a permission is missing, request only that permission and repeat the narrow check.
- If the wrong workspace appears, stop before running a tool and reconnect from the intended workspace.