> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/integrations/ai-assistants/connect-claude.md).

# Connect Claude to eMarketeer

Connect Claude to your eMarketeer account in about two minutes.

Connect Claude to your eMarketeer account in about two minutes.

You connect once on claude.ai. The Claude desktop app uses the same connectors, so it works there too.

## Before you start

* You log in to eMarketeer with your email address and password. Logins with Microsoft or SuperOffice don't work with the connector.
* Your Claude plan allows custom connectors.
* You have the connector address:

```
https://mcp.emarketeer.com/mcp
```

If your company manages Claude for you, follow Connect through your organization below. If Claude says "Organization owner must add this for the team", that's you. Otherwise, follow Connect on your own.

## Connect on your own

1. In Claude, open **Customize** and select **Connectors**.
2. Select **+ Add**, then **Add custom connector**.
3. Enter **eMarketeer** as the name and paste the connector address as the **MCP server URL**. Select **Continue**.
4. If Claude shows sign-in options, choose **Register automatically**.
5. Select **Add**.
6. Under **Yours**, select eMarketeer and choose **Connect**. The eMarketeer login page opens.
7. Log in with your eMarketeer email address and password. If you use multi-factor login, complete it.
8. Allow Claude to access your eMarketeer account.

## Connect through your organization

An owner of your company's Claude organization adds the connector once. Everyone else then connects to it.

If you are the owner:

1. In Claude, open **Organization settings** and select **Connectors**.
2. Select **+ Add** and add a custom web connector.
3. Enter **eMarketeer** as the name and paste the connector address. Select **Continue**.
4. If Claude shows sign-in options, choose **Register automatically**.
5. Select **Add**.

To connect, as the owner or any other member:

1. In Claude, open **Customize** and select **Connectors**.
2. Select **Yours**, then select eMarketeer.
3. Choose **Connect**. The eMarketeer login page opens.
4. Log in with your eMarketeer email address and password. If you use multi-factor login, complete it.
5. Allow Claude to access your eMarketeer account.

Don't add your own copy of the connector. Claude doesn't allow the same address twice in one organization.

## Check that it works

Start a new chat and ask:

> Which eMarketeer accounts do I have access to?

Claude lists the accounts you belong to. If it doesn't use eMarketeer, select **+** in the message box, then **Connectors**, and make sure eMarketeer is switched on.

## If you have several accounts

Name the account in your request, for example: "For the Acme Nordic account, how did our emails perform last month?"

## Disconnect

1. In Claude, open **Customize** and select **Connectors**.
2. Select **Yours**, then select eMarketeer.
3. Choose **Disconnect**.

Claude can no longer use your eMarketeer account.

## What to do next

* Try the [example requests](https://support.emarketeer.com/integrations/ai-assistants.md#examples).
* Something not working? See [AI assistants: troubleshooting](https://support.emarketeer.com/integrations/ai-assistants/troubleshooting.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.emarketeer.com/integrations/ai-assistants/connect-claude.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
