Skip to content
BuildBase
BuildBase in your AI tools

Use BuildBase in Lovable

BuildBase in your AI tools: connect Lovable to BuildBase's own MCP server and manage your BuildBase organization from Lovable. You sign in as yourself, and Lovable can do only what your role and your organization allow.

Add BuildBase to Lovable

The address is the same in every AI tool: https://api.console.buildbase.app/mcp. BuildBase signs you in the first time Lovable connects.

  1. In Lovable, add a remote MCP server: Connectors > Add custom > MCP server. Use the address https://api.console.buildbase.app/mcp.
  2. Sign in. OAuth is the default: choose Add & authorize and sign in.
  3. On BuildBase's sign-in page, sign in as you do to the console, then approve the consent screen, which names Lovable and what it asks for.
  4. Ask Lovable something, such as "List my BuildBase organizations."

The plan it needs

Custom MCP servers are on every Lovable plan. A workspace admin can turn them off; when MCP server is greyed out, ask the admin.

How sign-in looks in Lovable

OAuth is the default: choose Add & authorize and sign in.

What is different in Lovable

  • Lovable's custom MCP page does not document per-tool controls.
  • BuildBase adds its own rules on top: each organization is Off, Read only or Read and change for AI agents (Read only by default), and deletes, member and role changes, sends and money moves need your approval in the chat.
  • For a job with nobody to sign in, send one of your organization's API keys as the bearer instead. Choose bearer token or API key as the authentication.

If it does not work in Lovable

Lovable does not connect
A connection is yours alone: each teammate adds their own. It works in the chat, never in the published app.
Lovable says the organization does not let agents in
An owner or admin sets the organization's AI agents setting in the console, under Account, then Security. Off turns every agent away, and an owner or admin can also block one agent for one member there.
Lovable cannot change anything
The organization is Read only, the default. An owner or admin can switch it to Read and change, and Lovable can then make changes without signing in again. Deleting, sending to an audience, roles and money still ask you to approve each change.

Frequently Asked Questions

Which Lovable plan do I need?

Custom MCP servers are on every Lovable plan. A workspace admin can turn them off; when MCP server is greyed out, ask the admin.

Can Lovable change things in my BuildBase organization?

Only where the organization allows it: Read only is the default. Even then, deletes, member and role changes, sends and money moves need your approval in the chat, and secrets never reach Lovable.

Can I connect Lovable with an API key instead of signing in?

Yes, for a job with nobody to sign in: send one of your organization's API keys as the bearer. Choose bearer token or API key as the authentication. The key works in its own organization only, and the organization's AI agents setting still applies.

Where next