> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lovable.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect a custom MCP server as a chat connector

> Connect any remote MCP server to Lovable as a chat connector. Bring internal tools, private APIs, and custom data sources into the chat as live context while you build.

A **custom MCP server** is any remote server that supports the [Model Context Protocol](https://modelcontextprotocol.io) and is not already a prebuilt connector in the Lovable catalog. Connect one as a [chat connector (MCP server)](/integrations/chat-connectors), and Lovable can read from it as live context while you build: internal CRMs, private APIs, company knowledge bases, or niche third-party tools.

Custom MCP servers are available on **all plans**. Like all chat connections, they are personal to you, and they are never part of your published app. If your published app needs to call a service while people use it, use an [app + chat connector](/integrations/app-connectors) or [integrate the API directly](/integrations/any-api).

<Tip>
  Explore [remote MCP servers](https://mcpservers.org/remote-mcp-servers), a curated list of high-quality remote MCP servers compatible with Lovable.
</Tip>

## How to connect a custom MCP server

To connect a custom MCP server, you need the server's URL and, depending on the server, its credentials:

<Steps>
  <Step title="Open the custom MCP form">
    Open [**Connectors**](https://lovable.dev/dashboard?connectors), scroll to the bottom of the **All** view, and select the **Custom** card labeled **MCP** ("Connect your own MCP"). See [Where to find connectors](/integrations/introduction#where-to-find-connectors) for every place you can open the catalog.
  </Step>

  <Step title="Check the workspace suggestions">
    If someone in your workspace already connected a server, pick it from the **Used by others in this workspace** suggestions. This fills in the server details for you, and you can skip straight to authentication.
  </Step>

  <Step title="Name the server">
    Enter a clear **Server name** (for example, *Internal CRM* or *Analytics API*).
  </Step>

  <Step title="Enter the server URL">
    Enter the **Server URL** where Lovable can reach your MCP server, for example `https://mcp.example.com`.
  </Step>

  <Step title="Choose authentication">
    * **OAuth (default)**: Lovable uses OAuth by default. After you click **Add & authorize**, you're prompted to authorize.
    * **Bearer token or API key**: For servers that don't support OAuth, authenticate with a bearer token or API key.
    * **No authentication**: Connect without credentials if the server doesn't require authentication.
  </Step>

  <Step title="Add the server">
    Click **Add & authorize** (OAuth) or **Add server**. The custom MCP server now appears in your list of chat connectors and can provide contextual data for builds.
  </Step>
</Steps>

To confirm the connection works, ask Lovable something the server can answer, for example:

```text wrap theme={null}
Using the Internal CRM connector, list my five most recent customer accounts.
```

## Manage custom MCP servers

Custom MCP servers follow the same workspace controls as other chat connectors, through two settings:

* The **Custom MCP** row ("Allow members to connect their own MCP servers") in **Connectors → Admin settings → Chat connectors** turns custom MCP servers on or off for everyone. It governs them as a group, so individual custom MCP servers that members have connected do not appear in the admin table.
* [**Remote MCP connectors**](/features/privacy-and-security-settings#remote-mcp-connectors) in [Privacy & security](https://lovable.dev/settings/privacy-security) turns all chat connectors on or off for the workspace, custom MCP servers included.

See [Chat connector controls](/integrations/admin-controls#chat-connector-controls) for all chat connector governance settings.

## FAQ

<AccordionGroup>
  <Accordion title="Which plans support custom MCP servers?">
    All plans. Custom MCP servers are chat connectors, which are enabled by default everywhere, including on Enterprise workspaces. A workspace admin can turn them off with the **Custom MCP** setting described in [Manage custom MCP servers](#manage-custom-mcp-servers).
  </Accordion>

  <Accordion title="Can my published app use a custom MCP server?">
    No. Chat connections, including custom MCP servers, only give Lovable context while building. For functionality in your published app, use an [app + chat connector](/integrations/app-connectors) or ask Lovable to [integrate the API directly](/integrations/any-api).
  </Accordion>

  <Accordion title="Why doesn't my custom MCP server show up in Admin settings?">
    By design. The Admin settings table lists catalog connectors only. Custom MCP servers are controlled as a group through the **Custom MCP** row in **Connectors → Admin settings → Chat connectors**.
  </Accordion>

  <Accordion title="Can other people in my workspace use my custom MCP connection?">
    No. Chat connections are per-user. Others in your workspace can see the server in the **Used by others in this workspace** suggestions and connect it themselves with their own credentials.
  </Accordion>
</AccordionGroup>