Skip to content
BuildBase
Agent-ready apps

Let your users connect Cline to your app

Agent-ready apps: make the app you build with the SDK ready for Cline. Your users add your app's MCP server to Cline, sign in on your hosted page and approve it, and Cline acts as them, never as more.

How your users add your app to Cline

Give your users your app's MCP address. npx buildbase agent install --url <your MCP address> prints the setup for each AI tool, Cline included, with your address filled in.

  1. In Cline, your user adds a remote MCP server: MCP Servers > Remote Servers, or cline_mcp_settings.json. They use your app's MCP address, https://app.example.com/api/mcp in these examples, or the command or config below.
  2. Sign in. The Cline CLI's wizard offers Authorize OAuth and opens a browser.
  3. Your hosted sign-in page opens. Your user signs in and approves the consent screen, which names Cline and what it asks for.
  4. Cline can now use your tools, as that user and with that user's permissions.
cline_mcp_settings.jsonJSON
{
  "mcpServers": {
    "acme": {
      "type": "streamableHttp",
      "url": "https://app.example.com/api/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

  • Cline runs on your user's own computer, so it reaches any address that computer can, including a development server while you test.
  • Your server's built-in tools are read-only until you allow changes. autoApprove in cline_mcp_settings.json lists the tools Cline may run without asking.

If it does not work in Cline

Cline cannot register or sign in
Turn on Let agents register themselves, with a base client, in the console under Authentication, then Agent readiness. Cline registers its own client the first time it connects.
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.
Check your server the way Cline will
Run npx buildbase agent doctor --url <your MCP address>. It walks the first contact a client makes (the sign-in challenge, the metadata, redirects, a stable tool list) and exits 1 when a check fails.

Frequently Asked Questions

Which Cline plan do your users need?

Cline's documentation does not name a plan.

Does my MCP server need to be public for Cline?

No. Cline runs on your user's computer, so it reaches what that computer reaches. Your users still need an address they can open, and production should be public HTTPS.

Can Cline change data in my app?

Only through tools you allow, and only as the user who connected it. The built-in tools are read-only by default, and a tool that needs extra scopes is hidden until the user grants them.

Where next