Skip to content
BuildBase
BuildBase in your AI tools

Use BuildBase in Cline

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

Add BuildBase to Cline

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

  1. In Cline, add a remote MCP server: MCP Servers > Remote Servers, or cline_mcp_settings.json. Use the address https://api.console.buildbase.app/mcp, or the command or config below.
  2. Sign in. The Cline CLI's wizard offers Authorize OAuth and opens a browser.
  3. On BuildBase's sign-in page, sign in as you do to the console, then approve the consent screen, which names Cline and what it asks for.
  4. Ask Cline something, such as "List my BuildBase organizations."
cline_mcp_settings.jsonJSON
{
  "mcpServers": {
    "buildbase-console": {
      "type": "streamableHttp",
      "url": "https://api.console.buildbase.app/mcp"
    }
  }
}

The plan it needs

Cline's documentation does not name a plan.

How sign-in looks in Cline

The Cline CLI's wizard offers Authorize OAuth and opens a browser.

What is different in Cline

  • autoApprove in cline_mcp_settings.json lists the tools Cline may run without asking.
  • 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. Add --header "Authorization: Bearer <key>" to cline mcp add, or a headers object in cline_mcp_settings.json.

If it does not work in Cline

Cline does not connect
Set type to streamableHttp: without it Cline falls back to the older SSE transport. Check the address and raise the MCP timeout if it is slow.
Cline 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.
Cline cannot change anything
The organization is Read only, the default. An owner or admin can switch it to Read and change, and Cline 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 Cline plan do I need?

Cline's documentation does not name a plan.

Can Cline 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 Cline.

Can I connect Cline 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. Add --header "Authorization: Bearer <key>" to cline mcp add, or a headers object in cline_mcp_settings.json. The key works in its own organization only, and the organization's AI agents setting still applies.

Where next