> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant.md).

# Set up with an AI assistant

Connect Claude, Cursor or another AI assistant to your project on day one, and do the five Getting started steps with it: it reads, drafts and wires, you decide and confirm.

Connect Claude, Cursor or another AI assistant to your Jimo project before you build anything, and it becomes your onboarding coach: it reads your project, drafts experiences from your own plan, wires them together and tells you what is missing. You stay the one who decides, confirms and publishes, and a few things stay in the dashboard. Four words come back on this page: the MCP (Model Context Protocol) is the link between your assistant and your Jimo project, a connector is what you add in your assistant to plug it into a tool such as Jimo or Notion, your spec is the document where your onboarding plan is written, and `anchor:capture` is a line you run in your browser console to capture the element a step points at.

**You will have at the end:** an assistant connected to your project, with the permissions onboarding needs, and the five steps mapped to what it does and what you do.

{% hint style="info" %}
**Available from your trial.** The assistant's Jimo tools work from the first day of your trial, the same as on a paid plan.
{% endhint %}

***

## Why start with an assistant

The dashboard is where you see and position experiences. The assistant is where you describe them in plain language and let it do the repetitive part: drafting ten steps from a spec, wiring each checklist task to its tour, translating, tagging, checking what is live. Both work on the same project, with your own Jimo role: see [Two ways to drive Jimo](https://help.usejimo.com/docs/intro/what-is-jimo/how-jimo-fits-together.md#two-ways-to-drive-jimo).

It pays off most when:

* Your onboarding plan already lives in a document (a spec in Notion, a Google Doc, a slide), and you do not want to copy it by hand.
* You build a journey of several experiences that launch each other.
* You want a second reading of what you built before you publish: what does each button launch, which step points at which element, which language is missing.

#### Your assistant is not the Agent

The [Agent](https://help.usejimo.com/docs/experiences/agent.md) is the chat Jimo puts in your product for your users. Your assistant is the AI tool you already use at work, connected to Jimo through the [MCP](https://help.usejimo.com/docs/integrations/mcp.md). Your users never see it.

## Connect it

{% stepper %}
{% step %}

### Copy the endpoint and add the connector

In **Settings > Integrations > Model Context Protocol**, copy the MCP Endpoint URL and add it to your assistant as a custom connector. The exact steps for Claude, Claude Code and Cursor are in [Connect an AI assistant](https://help.usejimo.com/docs/integrations/mcp/connect-an-ai-assistant.md). About two minutes.
{% endstep %}

{% step %}

### Pick the project and the permissions

On the approval page, pick your project. For onboarding, keep **Read project data and analytics** and **Manage Experiences**. Leave the two Agent permissions for later: you can add them by connecting again. See [Permissions and safety](https://help.usejimo.com/docs/integrations/mcp/permissions-and-safety.md).
{% endstep %}

{% step %}

### Ask a first question

"Give me an overview of this project: environments and their domains, what is live, what is in draft." The answer tells you the connection works and which project you are on.
{% endstep %}
{% endstepper %}

Connecting needs the Integrations access in your Jimo role. See [Roles and permissions](https://help.usejimo.com/docs/getting-started/your-workspace/roles-and-permissions.md).

## Connect what sits next to Jimo

Jimo never reads your other tools. Your assistant does, with its own connectors, and passes the text to Jimo.

| Connect                                                            | So the assistant can                                                                             |
| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------ |
| Your spec: a Notion page, a Google Doc, a file you upload          | Build from your plan, then compare what is built with what is written                            |
| Your list of user attributes (plan, role, signup date)             | Write the handoff your developer needs at Step 4                                                 |
| Your codebase, through Claude Code, Cursor or another coding agent | Install the snippet and the identify call with the prompt from **Get Started > 4. Install Jimo** |

What to put in the spec, and how to name things so the assistant finds them, is in [Working with your spec and your team](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant/working-with-your-spec-and-your-team.md).

## The five steps from your assistant

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FbXmHDlioj1CVjcW4wj8H%2FA-02-five-steps-assistant.png?alt=media&amp;token=e8a36185-c4b1-4e6d-b452-45a71a2d0a56" alt="The five Get Started steps, workspace to publish, with what the assistant does and what stays with you at each one, every change previewed then confirmed"><figcaption></figcaption></figure>

{% stepper %}
{% step %}

### Your workspace

**The assistant:** reads the environments and their domains, lists the drafts already in the project, and flags a domain typed with `https://` or a path.

**You:** invite your team and fix a domain in the dashboard. See [Your workspace](https://help.usejimo.com/docs/getting-started/your-workspace.md).
{% endstep %}

{% step %}

### Install the Chrome extension

**The assistant:** nothing here. It drafts and edits, it does not see your screens.

**You:** install the extension, so you can open drafts on your own app. See [Install the Chrome extension](https://help.usejimo.com/docs/getting-started/install-the-chrome-extension.md).
{% endstep %}

{% step %}

### Create an experience

**The assistant:** drafts the experiences from your spec, sets what each button and task launches, and gives you a preview link.

**You:** capture the elements that steps point at, walk the preview, and say what to change. See [Create your first experience](https://help.usejimo.com/docs/getting-started/create-your-first-experience.md).
{% endstep %}

{% step %}

### Install Jimo

**The assistant:** writes the handoff for your developer: the attributes to send, and the element each step points at.

**You or your developer:** add the snippet and the identify call, by hand or with a coding agent. See [Install Jimo](https://help.usejimo.com/docs/getting-started/install-jimo.md).
{% endstep %}

{% step %}

### Publish

**The assistant:** targets a test segment with the number of users it reaches, then publishes to the environment you name, after a preview.

**You:** confirm each change, check on your app that it shows, then widen. See [Publish your first experience](https://help.usejimo.com/docs/getting-started/publish-your-first-experience.md).
{% endstep %}
{% endstepper %}

The prompts for each step are in [Prompt library: setup](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant/prompt-library-setup.md).

## What stays in the dashboard

| Task                                        | Why                                                                                     | Where                                                                                                                                                |
| ------------------------------------------- | --------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| Rename an experience                        | The assistant edits an experience's copy, not its name                                  | The experience, in the dashboard                                                                                                                     |
| Create or edit a segment                    | The assistant targets saved segments, it does not create them                           | [Users & Segments](https://help.usejimo.com/docs/analyze/users-and-segments.md)                                                                      |
| Put an experience in a Space                | Not available to the assistant, it can tag instead                                      | [Spaces](https://help.usejimo.com/docs/build/spaces.md)                                                                                              |
| Fine styling: one step's colors, fonts, CSS | The assistant applies a whole project theme, which replaces styling made in the builder | The builder, after any theme change                                                                                                                  |
| Write a CSS selector                        | The assistant never writes a selector                                                   | Your app's console, with `anchor:capture`, then paste it to the assistant                                                                            |
| Invite your team, fix a domain              | Settings are out of the assistant's reach                                               | [Settings > Team](https://help.usejimo.com/docs/settings/team-management.md), [Environments](https://help.usejimo.com/docs/settings/environments.md) |

The full list is in [Permissions and safety](https://help.usejimo.com/docs/integrations/mcp/permissions-and-safety.md#what-stays-outside-the-assistant).

{% hint style="warning" %}
**The most common surprise: a theme applied from the assistant.** It rewrites the colors, fonts and spacing of every step, including what you styled by hand in the builder. Pick the theme first, from the assistant or in the builder, then do the fine styling last.
{% endhint %}

## Hand over to your team

Ask the assistant to tag what it built, for example **Needs review** on an experience a colleague or your Jimo contact should check, and **Needs help** on one it could not finish. They filter the experience list on the tag and pick up from there. Tags are set one experience at a time and are never shown to your users. Conventions and the split of roles are in [Working with your spec and your team](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant/working-with-your-spec-and-your-team.md).

## Verify

* Your assistant lists the Jimo tools, and an overview question names your project and its environments.
* A test request such as "draft a modal named Test, then show me its copy" creates a draft in your dashboard, invisible to your users. Delete it in the dashboard afterwards.
* You know who on your team captures elements, who installs, and who confirms publications.

## Go further

* [Prompt library: setup](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant/prompt-library-setup.md): one prompt per setup task, ready to copy.
* [Prompt library: routines](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant/prompt-library-routines.md): the weekly checks, the call prep, the release routine.
* [Working with your spec and your team](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant/working-with-your-spec-and-your-team.md): spec, naming, tags, who does what, and a playbook to paste in your assistant.
* [What to ask](https://help.usejimo.com/docs/integrations/mcp/what-to-ask.md) and [Tools reference](https://help.usejimo.com/docs/integrations/mcp/tools-reference.md) in the MCP section.

**Next page:** [Step 1, Your workspace](https://help.usejimo.com/docs/getting-started/your-workspace.md)
