Skip to main content
MCP (Model Context Protocol) is an open standard that connects AI systems, like Lovable, to external tools, services, and data sources. In Lovable, MCP servers are used as chat connectors. By connecting Lovable to tools such as Notion, Atlassian, or Linear, the Lovable Agent can use real team context to generate more accurate code, prototypes, and documentation. When connected, Lovable can read structured data (like text from docs, issues, or diagrams) and, where supported, perform limited actions such as creating or updating items. Lovable includes several prebuilt chat connectors and supports custom MCP servers on all plans.

Why use chat connectors

Chat connectors unlock two key capabilities:
  • Bring your existing context into Lovable.
    The Lovable Agent can read your team’s documentation, tickets, and design files to build prototypes and flows aligned with your standards.
  • Connect your Lovable apps to your workflows.
    The Lovable Agent can take follow-up actions in your connected tools, such as updating ticket statuses, adding prototype links as comments, or creating new items when supported.
Lovable becomes more powerful when it understands your team’s world, eliminating guesswork, speeding up iteration, and helping you go from idea to live app faster than ever.

Prebuilt chat connectors

How to add a prebuilt chat connector

To use prebuilt integrations with popular third-party apps and services:
  1. Open ConnectorsChat connectors.
  2. Select a chat connector (for example, Notion or Linear).
  3. Click Connect. Sign in and grant Lovable access to your account.

Additional setup for specific chat connectors

n8n In addition to these steps, you need to do the following in n8n:
  • Go to Settings → MCP access and toggle Enable MCP access (requires instance owner or admin permissions)
  • For each workflow you want to expose, go to Settings in the workflow editor and toggle Available in MCP.
Amplitude If you plan to analyze your Lovable-built app, make sure it is already sending data to Amplitude before using the MCP connector. See the Amplitude Quickstart guide for setup instructions. Hex Hex requires you to provide a custom server URL when connecting. For most users, the default URL is https://app.hex.tech/mcp. If you are on a single-tenant, EU multi-tenant, or HIPAA multi-tenant instance, replace app.hex.tech with your custom Hex domain (for example, https://your-company.hex.tech/mcp or https://eu.hex.tech/mcp).

Custom MCP servers

For full flexibility, you can connect custom MCP servers as chat connectors to bring internal or third-party systems into Lovable. This is perfect for private APIs, internal CRMs, or custom data sources. Explore remote MCP servers, a curated list of high-quality remote MCP servers compatible with Lovable.

How to connect a custom MCP server

To connect a custom or internal MCP server:
  1. Open Connectors and go to Chat connectors.
  2. Click New MCP server.
  3. Server name: Enter a clear name for your server (for example, Internal CRM or Analytics API).
  4. Server URL: Enter the address where Lovable can reach your MCP server.
  5. Authentication:
    • OAuth (default): Lovable uses OAuth by default. After you click Add & authorize, you’ll be prompted to authorize.
    • Bearer token or API key: For servers that don’t support OAuth, you can authenticate using a bearer token or API key.
    • No authentication: Connect without credentials if the server doesn’t require authentication.
  6. Add server. The custom MCP server now appears in your list of chat connectors and can provide contextual data for builds.

Practical examples

Each connected app instantly becomes available as context for the Lovable Agent. You can interact with connected tools using natural prompts.

Security and permissions

Chat connectors (MCP server connections) are per-user connections. You can review or revoke them anytime in Connectors. For quick access inside a project, click + in the prompt box and go to Connectors. On Business and Enterprise plans, workspace admins and owners can manage which servers are available as chat connectors for all users:
  • Go to Settings → Privacy & security to enable or disable all MCP server access for the entire workspace.
  • Open ConnectorsChat connectorsAdmin settings to enable or disable individual MCP servers as chat connectors.