Name your workspace

Sign-up ends on Name your workspace, which creates the tenant. Enter a name; the address below the field is derived from it and is shown as you type (accented letters are written plain, so “Café Analytics” becomes cafe-analytics). Neither can be changed afterwards. If the name has no Latin letters or numbers to build an address from, an Address field appears so you can choose one. If the address is already taken, the page says so and you pick a different name or address. Let’s go creates the workspace and opens its Overview. If you signed up while following a link to another page, that page opens instead. If you create your workspace while connecting an MCP client, you return directly to its consent screen. The welcome questions appear when you next open the Overview. Pending invitations stay available in the Overview before the welcome questions. If invitations could not be loaded, retry their notice there before continuing setup.

Start in your coding agent

Right after sign-up, a short form asks which coding agents you use. Tick any of Claude Code, Codex and Cursor (the agents dip registers itself with), or scroll the same list for any of the others (Claude Desktop, Claude.ai, GitHub Copilot, Gemini CLI, Windsurf and more, or Another MCP client). If you created the workspace, the next question asks where your data lives; the last asks your team. The Overview then shows those agents first; the rest stay one click away. A new workspace’s Overview leads with one card, Get started, built around the way most people set Dippr up: not by hand, but by handing their own coding agent one prompt.
1

Pick your agent

Choose Claude Code, Codex, Cursor or Other agents. The choice only changes which Open in … link the card offers and which agent the template gallery below targets; the prompt is the same for all of them.
2

Copy the prompt

Click Copy prompt and paste it into your agent, or click Open in Claude Code ↗ (Codex and Cursor have the same link) to open the agent with the prompt filled in. The prompt names your workspace and tells the agent to read your workspace’s own /agents.md, which carries the install command for your workspace’s dip release, the sign-in step and the connection check. The agent installs dip, runs dip login with your workspace address, and registers the workspace’s MCP server with itself. You approve the sign-in in your browser; nothing else is typed by hand.With Other agents there is no link to open; paste the prompt into the agent’s chat, and once it has run, add the server URL it prints to that agent’s MCP settings.
3

Watch the card follow along

The Get started in your coding agent panel at the top of the Overview has your agents across its top; Other agents opens a picker with every other agent, the same list as the sign-up form. Below the prompt, Copy prompt (and Open in for Claude Code, Codex and Cursor). Under the panel, side by side: Connect your data, with the sources you picked when you signed up first and every other source the workspace can read under Also works with, each one click from its connection form; and Start from a template, with a team filter and Browse all (four templates, or six on a wide screen). The Overview opens with the sidebar collapsed to give these the room. The Setup counter in the panel’s footer ticks on its own as the workspace sees your agent connect, your data become readable and your first app go live. Later hides the setup; a one-line reminder with Continue setup stays on the Overview until it is done.Data connected ticks once a data source is connected and a query engine has its catalogs loaded, so your agent can actually query it. A source with no engine, or an engine that has not loaded any catalogs yet, leaves the step open, and the card says which one and links to the fix.
4

Restart your agent, then paste the continuation

An agent session that was open while dip login ran never sees the newly registered MCP server; dip says so in its output. Once the card sees your sign-in it swaps its prompt for a continuation: restart the agent, paste After restarting …, paste this, and the agent checks its Dippr tools, runs SELECT 1 and helps you ask a first question. You never have to compose that message yourself.
5

Build something

Once an AI tool has queried the workspace the card says Your agent is connected and the Start from a template gallery below it is the next step: each template is a complete prompt for a live data app, filtered by team, with Copy prompt and an Open link for the agent you picked. Or just ask your agent a question. When the first app is live the card collapses to a one-line is live strip with Open your apps and Invite a teammate.
A workspace needs something to query before the agent can answer a question. If you have no source to connect yet, click Use sample data · Avocado prices on the card; Dippr adds a small read-only sample catalog hosted for you. Or let your agent ask: when it finds nothing connected it offers the sample itself. Connecting your own source is Connect a source on the card, or Data sources → Add integration.

The step-by-step checklist

The Overview no longer links to it, but the step-by-step checklist is still there for people who prefer the terminal to the agent: add ?manual=1 to the Overview address. It has Connect your data, Bring your terminal and AI tool (the install one-liner, dip login, and the manual claude mcp add alternative), and Build your artifact, publish it as an app. Each step completes on its own when the workspace sees it happen; Back to the one-prompt setup returns. The checklist is also what a role without the create grants sees, trimmed to the steps it can act on. Later hides the card for this browser; Continue setup on the Overview brings it back.

Add the sample dataset

To run a real query before connecting your own data, click Use sample data on the Get started card. Dippr adds the Avocado prices (sample) dataset as a read-only source. To query it you then need a query engine; on a workspace Dippr runs for you, the first query engine gets the sample added automatically before it starts, so it is there with no extra restart. It isn’t added again for later engines, so if you remove it, it stays removed. Workspaces whose data plane runs in your own cloud account don’t get it automatically. The sample is added as yours, so it is added only if your role lets you create workspace databases. If it doesn’t, the engine is still created without the sample, and Dippr tells you why when the engine is registered. If Dippr can’t check your permissions at that moment, it skips the sample the same way and you can add it later with Use sample data. The sample then appears in Data sources → Connected, tagged Sample, with the kind Sample dataset. Select its name to open its detail page. Because the data is hosted by Dippr, Test connection is disabled. Connected appears once you have at least one source; until then, Data sources opens on Add integration. The Quickstart walks through querying it.

Use your own data

  1. Follow the Quickstart to connect a source and prepare an engine.
  2. Connect an AI agent if you did not let the prompt do it.
  3. Ask your question, then build an app and install it. Building needs Docker and a running daemon; see Prerequisites.
Your real apps query data using the viewer’s access. The sample remains available after you add real sources or publish an app.