> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-greatstore/get-started/quickstart.md).

# Quickstart

The admin home page tracks five setup steps. This page walks all five, in order. You can stop after step 3 and have a working assistant — steps 4 and 5 make it better.

{% hint style="success" %}
**Estimated time: 15 minutes.** You'll need admin access to your Greatstore store and the ability to add a `<script>` tag to your site.
{% endhint %}

{% embed url="<https://vimeo.com/1216097590>" %}
The five setup surfaces, in order
{% endembed %}

## Before you start

* [x] A provisioned Greatstore store (the Greatstore team sets this up — you'll get `<your-slug>.greatstore.ai/admin`)
* [x] Admin of the store's organization in Maker Nav — that's the sign-in
* [x] Somewhere to paste a script tag — your theme, your CMS, or a tag manager
* [x] Your brand assets: an icon, and a logo for light and dark backgrounds

## Steps

{% stepper %}
{% step %}

#### Configure your assistant

Go to **Configure → Basic** and set your brand name, website, and logos.

The **brand name** appears in the chat header and is how the assistant refers to your store. The **assistant name** is optional — give it one and it introduces itself by name, leave it blank and it speaks generically as the store.

{% hint style="info" %}
On the demo store the assistant is called **M.** — that's the assistant name in action.
{% endhint %}
{% endstep %}

{% step %}

#### Connect a data source

Go to **Connectors**. Greatstore ships with **Maker MCP** enabled by default, which gives the assistant product discovery against your store.

Leave it on unless you're running entirely on your own connectors. Order matters — when two connectors expose a tool with the same name, the one higher in the list wins.

Select any connector to see the tools it offers, and allow or disallow them per group or one by one — worth doing if you connect a server that does more than shopping.

See [How connectors work](/maker-greatstore/connectors/how-connectors-work.md) and [Controlling tool access](/maker-greatstore/connectors/tool-access.md).
{% endstep %}

{% step %}

#### Set up your knowledge base

Go to **Knowledge** and add the documents your catalogue can't answer from — returns policy, shipping, sizing, care instructions.

You can attach files, add a page by URL, or paste a note. Up to **10 sources**.

Then use the chat on the same screen to test a question against them.

{% hint style="warning" %}
Testing here uses the same AI as your live store, so it draws from your credits like any other message.
{% endhint %}
{% endstep %}

{% step %}

#### Build or install an app

Apps are interactive components the assistant can render inside the chat — a comparison table, a catalogue grid, a product card.

{% tabs %}
{% tab title="Install a ready-made app" %}
Browse [App library](/maker-greatstore/apps/library.md) and install one. Nothing to build — it becomes available to the assistant immediately.
{% endtab %}

{% tab title="Build your own" %}
Follow [Building an app](/maker-greatstore/apps/building-an-app.md). You publish components over MCP and they appear in **Apps** with a live preview.
{% endtab %}
{% endtabs %}

This step is optional — the assistant works without any apps, it just answers in text.
{% endstep %}

{% step %}

#### Install the embed on your site

Paste this before the closing `</body>` tag on every page where you want the assistant:

```html
<script src="https://demo.greatstore.ai/embed.js"></script>
```

The assistant loads in the background and stays hidden until a shopper opens it — no layout shift, nothing visible until they tap the chat bubble or you call `open()`.

Full details in [Install the chat widget](/maker-greatstore/get-started/install-the-widget.md).
{% endstep %}
{% endstepper %}

## Check it worked

Open your storefront and look for the chat bubble. Send a question you know is answered by one of your knowledge sources — a returns question is usually the quickest test.

Then go back to **Chats** in the admin. Your conversation should be listed there within a few moments.

## What's next?

{% content-ref url="/pages/qeUjDc1d2wR9NZJGCqdD" %}
[Appearance](/maker-greatstore/configure/appearance.md)
{% endcontent-ref %}

{% content-ref url="/pages/KGMX4QPP4jpUtW33JVAR" %}
[Usage & credits](/maker-greatstore/insights-and-usage/usage-and-credits.md)
{% endcontent-ref %}

{% content-ref url="/pages/Mf90Eudy8wqnmesbEaFu" %}
[JavaScript API](/maker-greatstore/developer-reference/javascript-api.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.maker.co/maker-greatstore/get-started/quickstart.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.