Skip to content
BuildBase
BuildBase in your AI tools

Use BuildBase in Claude

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

Add BuildBase to Claude

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

  1. In Claude, go to Customize > Connectors, choose + Add, then Add custom connector. On Team and Enterprise, an owner does this under Organization settings > Connectors.
  2. Enter a name and the address https://api.console.buildbase.app/mcp, then choose Continue.
  3. Under Authentication, choose Sign in when needed (or Sign in now).
  4. Under OAuth client, choose Register automatically. The default, Claude's published identity, does not work with BuildBase's server.
  5. Choose Add, then Connect, and sign in. In a chat, turn the connector on from + > Connectors.

The plan it needs

Custom connectors are on every Claude plan, Free included; Free is limited to one. On Team, only Owners and Primary Owners add one; on Enterprise, Owners, Primary Owners and roles with "Manage access to Libraries". Once an admin adds it, each member connects it themselves.

How sign-in looks in Claude

Under Customize > Connectors, find the connector and choose Connect. A browser page opens for sign-in, and Claude never sees the password.

What is different in Claude

  • Under Customize > Connectors > the connector > Tool permissions, set each tool, or the read-only and write groups, to Always allow, Needs approval or Blocked. On Team and Enterprise an Owner sets these for everyone.
  • 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. The connector's Request headers field takes a bearer token, sent with every request. On Team and Enterprise everyone shares that one credential, so use one with limited access.
  • One connector works on claude.ai and in Claude Desktop. Turn it on in a chat from + > Connectors.

If it does not work in Claude

Claude needs to sign in again
Disconnect the connector under Customize > Connectors and connect it again. To change its address or settings, remove it and add it again.
Claude does not connect
Claude connects from Anthropic's cloud, not from your computer: a server on a private network, behind a VPN or behind a firewall that does not allow Anthropic's addresses cannot be reached.
Claude 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.
Claude cannot change anything
The organization is Read only, the default. An owner or admin can switch it to Read and change, and Claude 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 Claude plan do I need?

Custom connectors are on every Claude plan, Free included; Free is limited to one. On Team, only Owners and Primary Owners add one; on Enterprise, Owners, Primary Owners and roles with "Manage access to Libraries". Once an admin adds it, each member connects it themselves.

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

Can I connect Claude 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. The connector's Request headers field takes a bearer token, sent with every request. On Team and Enterprise everyone shares that one credential, so use one with limited access. The key works in its own organization only, and the organization's AI agents setting still applies.

Where next