Connecting to an engine means pointing a SQL client, notebook or script at its endpoint, using whichever of the supported methods below matches how that client authenticates. Open an engine and choose Connect (or Connect… in the row menu) for copyable snippets, filled in with that engine’s real endpoint. Clients connect directly to the engine — query results never pass through Dippr’s control plane.
For a human at a terminal. The engine sends you to your tenant to sign in, then keeps your session alive on your behalf — a long query keeps working while it runs and while you page through its results, with nothing to re-run when a token expires.
Trino CLI

Host, port and TLS

An engine’s endpoint is https://<engine-id>.engine.<plane-domain>:8443 in most deployments — always copy it from the console or dip engine list rather than composing it by hand, since the port and domain vary by deployment. It’s always TLS; there’s no plaintext option.
Against a local development cluster, the endpoint uses a self-signed certificate. The Connect dialog appends --insecure (or the equivalent trust-off flag) automatically for a dev endpoint — you shouldn’t need to add it yourself against a real deployment.

AI agents

Claude Code, Codex, Cursor and similar agents reach your tenant through its MCP server, not an engine’s own endpoint directly. dip login registers that server with the agents on your machine; run dip mcp install to add another agent or redo it. See Connect Claude (or another agent). A headless agent with no interactive login instead uses a service user’s API key, with query_engines:execute_sql and metadata:read, exported as DIPPR_API_KEY.

Why does a hand-rolled client die mid-query?

The Trino wire protocol re-presents your bearer token on every poll of a running query’s results, not just at the start. When a token expires mid-session, the coordinator answers the next poll with a 401 naming a token endpoint to refresh from, with no browser step needed. The CLI, JDBC driver and Python client all handle this automatically. A client you’ve written by hand against the raw REST protocol has to handle that one exchange itself, or it will die mid-query the moment a token expires — that isn’t a bug in the engine.

Engine sign-in and OAuth

How a person and a machine each authenticate to an engine.

Connect an AI agent

How Claude Code, Codex and Cursor reach your tenant through MCP instead.