> ## Documentation Index > Fetch the complete documentation index at: https://docs.consile.ai/llms.txt > Use this file to discover all available pages before exploring further. # Connect Claude > Add each Consile MCP as a custom connector in Claude, Claude Desktop or Claude Code. *[Læs siden på dansk](https://docs.consile.ai/connect/forbind-claude.md)* For Claude to talk to a connector, you add its Consile address as a **custom connector** in Claude. Each MCP you buy has its own address and becomes its own connector in Claude with only its own tools. You repeat the steps for each MCP you want to use. > [!NOTE] > > Custom connectors are available on every Claude plan: Free, Pro, Max, Team and > Enterprise. On Claude Free you can only have one custom connector. If you want to > use more than one Consile MCP, or Concierge alongside, you need Pro, Max, Team or > Enterprise. A connector follows your Claude account, so you can also use it in > Claude Desktop and the Claude mobile app. The menu names are given in English > here and may change. See also Anthropic's guide > [Get started with custom connectors using remote MCP](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp). ## Find the address in the portal The address is in the [portal](https://app.consile.ai) on the connector's page in the **Add it to your AI assistant** card, and on the **Subscription activated** page right after a purchase. The Concierge address is under **Account** › **Settings** in the **Consile Concierge** card. The addresses look like this: ``` https://mcp.consile.ai/mcp # Consile Concierge (management) https://mcp.consile.ai/gsc/mcp # Google Search Console https://mcp.consile.ai/economic/mcp # e-conomic https://mcp.consile.ai/economic-2/mcp # e-conomic, agreement 2 (only if you have an extra agreement) ``` The top address is [Concierge](https://docs.consile.ai/en/concierge.md), your management connector. > [!NOTE] > > The address is the same for every Consile customer. Your Consile login and the > access an administrator has given you decide which organization and which data > your AI gets access to. If you have extra agreements for the same connector (each > agreement is one connected account), agreement 2 onwards each have their own > address. You copy it with the copy icon next to the agreement on the > **Connections** card on the connector's page, and you add it as a separate > connector. ## Claude Free, Pro and Max **1. Open Connectors** In Claude: go to [**Customize → Connectors**](https://claude.ai/customize/connectors). **2. Add a custom connector** Click **+ Add** and then **Add custom connector**. Give the connector a name, for example "Consile e-conomic", paste the address from the portal, and click **Continue**. **3. Choose login settings** Claude shows the login settings it has found. Click **Continue**. Under **Authentication**, choose an option with login, for example **Sign in now**, not **No sign in**. Under **OAuth client**, choose **Register automatically**, not the default **Use Claude's published identity**. Leave the **Request headers** field empty, and click **Add**. **4. Log in to Consile** Claude opens Consile's login. If you are already logged in to the portal in the same browser, Consile uses that user and organization. Otherwise you log in the same way as in the portal and choose your company's organization if you are asked. Then approve that your AI client may act on your behalf at Consile. You are sent back to Claude automatically. > [!TIP] > > Start a new conversation. The connector's tools are now available. Repeat the > steps with another address to add more MCPs. > [!NOTE] > > The login settings cannot be changed after the connector has been added. If login > fails, remove the connector under **Customize → Connectors** (on Team and > Enterprise under **Organization settings → Connectors**) and add it again with > **Register automatically**. If a colleague is logged in to the portal in your > browser, log out of the portal first, so Claude is linked to your own login. ## Claude Team and Enterprise On Team and Enterprise, an owner of the Claude organization (Owner or Primary Owner) adds custom connectors. On Enterprise it can also be a user with a custom role that gives access to manage the organization's **Libraries**. **1. The owner adds the connector once** The owner goes to [**Organization settings → Connectors**](https://claude.ai/admin-settings/connectors), clicks **Add**, chooses **Custom** and then **Web**. The owner gives the connector a name, pastes the address and clicks **Continue**. Under **Authentication**, the owner chooses an option with login, and under **OAuth client**, **Register automatically**. Finally the owner clicks **Add**. **2. Each employee connects themselves** Each employee goes to **Customize → Connectors**, finds the connector with the **Custom** label, clicks **Connect** and logs in with their own Consile login. The address is the same for everyone in the company, so the owner adds each MCP once. That the connector exists in your Claude organization does not give access to data. Each employee logs in with their own Consile login, and Consile decides the access (see [Colleagues and access](#colleagues-and-access)). ## Use the connector in a conversation Click **+** in the chat field, choose **Connectors**, and turn on the connectors you want to use in the conversation. If you have not connected the data source yet, Claude answers with a link to connect it. The link works for 10 minutes. You can also click **Connect now** on the connector's page in the portal. You always connect Shopify in the portal, because the store's domain has to be entered there. CVR does not need to be connected; it works as soon as it is bought. > [!TIP] > > When Claude asks for permission to use a tool, you can choose **Allow always** for > the tools you trust. On Team and Enterprise, the owner can also set permissions > per tool for the whole organization. Consider giving only the read tools free > access, and let the tools that change data require your approval. See > [Actions & guardrails](https://docs.consile.ai/en/essentials/actions-and-guardrails.md). ## Claude Code Choose **Claude** on the **Add it to your AI assistant** card on the connector's page in the portal, and copy the command in the **Claude Code** field. Right after a purchase you can also click **Copy Claude Code command** on the **Subscription activated** page. The command looks like this: ```bash theme={null} claude mcp add --transport http consile-gsc https://mcp.consile.ai/gsc/mcp ``` Run it in your terminal. Then open `/mcp` in Claude Code, choose the server, and log in to Consile. Under **Account** › **Settings** you find the matching command for Concierge. ## Colleagues and access The subscription belongs to the company, and your data source is connected only once. Colleagues do not need to buy the connector again and do not need to connect e-conomic, Google and so on again. **1. Invite the colleague** An administrator invites the colleague under **Team** in the portal. The invitation is free. The colleague accepts the invitation from the email. **2. Give access** The administrator gives the colleague access to the MCPs they need, on the person's page under **Team**. The person who bought the connector already has access. Each extra user costs 50% of the connector's monthly price and is billed pro rata from the day access is given. The portal shows the price and asks for confirmation first. If you have the [Consile Studio membership](https://docs.consile.ai/en/portal/membership.md), the administrator gives the colleague a membership licence instead (see [Membership licence](https://docs.consile.ai/en/portal/team.md#membership-licence)). For e-conomic and Uniconta, the administrator also chooses an access level: **Read only** or **Full access**. On every connector, the administrator can also choose **Custom** and pick exactly the tools the colleague gets. All levels cost the same. **3. The colleague connects their own AI** The colleague first logs in to the portal through the link in the invitation, so they end up in the company's organization. Then the colleague adds the same address in their own Claude (on Team and Enterprise, the colleague clicks **Connect** on the connector the owner has added) and logs in with their own Consile login. > [!WARNING] > > If the colleague has not been given access, Claude still shows the connector's > tools, but every call is refused with a message to ask an administrator for > access under **Team**. Access works a few seconds after it has been given. If the > colleague logs in without an invitation, a new, empty organization may be created, > and Claude answers that there is no subscription. Do not buy the connector again: > ask your administrator for an invitation. > [!NOTE] > > If the administrator changes a user's access level, the user must start a new > conversation so Claude fetches the updated list of tools. With **Read only**, > Claude only shows the tools that read data, and Consile blocks all write > operations on the server for that user. More on roles, access and prices in [Team](https://docs.consile.ai/en/portal/team.md) and [Pricing](https://docs.consile.ai/en/portal/pricing.md). ## Next steps Claude is now connected, but does not yet know which data it may read. That is decided when you connect your specific data source: > **[Connect your account](https://docs.consile.ai/en/connect/connect-your-account.md)** > > How to give Consile access to your data source, depending on the connector. > **[Do you use ChatGPT?](https://docs.consile.ai/en/connect/connect-chatgpt.md)** > > The same address works in ChatGPT through Developer mode. > **[Microsoft 365 Copilot](https://docs.consile.ai/en/connect/connect-microsoft-copilot.md)** > > e-conomic is available as a Copilot agent in a pilot version. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.