> 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/connectors/adding-your-own.md).

# Adding your own connector

Connectors are data sources for the assistant. Anything that speaks MCP can plug in — a commerce platform's catalogue, a third-party service, or an API you already run, wrapped as an MCP.

## What people connect

| Connector                           | What it unlocks                                                                                                                  |
| ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Shopify's public catalog MCP**    | Product discovery for any Shopify store — no Maker Nav required. Disable Maker MCP and use this instead.                         |
| **A currency-conversion MCP**       | The reference storefront uses one (a forex MCP) so the assistant can convert prices on request.                                  |
| **Your own API, wrapped as an MCP** | Example: a retailer with a size-guide API exposes it as an MCP, and the assistant can answer "will this fit me?" with real data. |

{% embed url="<https://vimeo.com/1216097612>" %}
Adding a connector, and where it lands in the order
{% endembed %}

## Adding one

{% stepper %}
{% step %}

#### Give it an endpoint

The MCP server URL, for example:

```
https://object-detection-mcp.maker.workers.dev/mcp
```

{% endstep %}

{% step %}

#### Set authentication

Bearer auth is supported — connectors using it show a `BEARER` badge in the list.
{% endstep %}

{% step %}

#### Place it in the order

Higher wins on tool-name collisions — put yours above Maker MCP to override a tool.
{% endstep %}

{% step %}

#### Revalidate

The refresh button beside **Add connector** confirms the server responds and its tools are picked up.
{% endstep %}

{% step %}

#### Choose which tools it may use

Select the connector to see its tools, sorted into write, read-only and other. Allow or disallow them per group, or one at a time — see [Controlling tool access](/maker-greatstore/connectors/tool-access.md).

This is what makes it safe to connect an MCP you already run internally: expose only the tools a shopping assistant needs, and leave the rest unreachable.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Every **allowed** tool is a capability handed straight to the AI. Slow connectors make slow answers — the assistant waits on your server — so keep latency in mind, and disallow what you don't need.
{% endhint %}

{% hint style="warning" %}
If your connector's components load scripts or call other origins in the browser, add those hosts under [Security](/maker-greatstore/configure/security.md) or the storefront CSP will block them.
{% endhint %}


---

# 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/connectors/adding-your-own.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.