Skip to content
BuildBase
Agent-ready apps

Let your users connect Junie to your app

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

How your users add your app to Junie

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

  1. In Junie, your user adds a remote MCP server: .junie/mcp/mcp.json or ~/.junie/mcp/mcp.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 server shows Authorization required. Run /mcp, choose it, then Authorize, and sign in in the browser; it turns Active.
  3. Your hosted sign-in page opens. Your user signs in and approves the consent screen, which names Junie and what it asks for.
  4. Junie can now use your tools, as that user and with that user's permissions.
.junie/mcp/mcp.jsonJSON
{
  "mcpServers": {
    "acme": {
      "url": "https://app.example.com/api/mcp"
    }
  }
}

The plan it needs

JetBrains' Junie MCP page does not name a plan.

How sign-in looks in Junie

The server shows Authorization required. Run /mcp, choose it, then Authorize, and sign in in the browser; it turns Active.

What is different in Junie

  • Junie 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. Junie's MCP page does not document per-tool controls.
  • The Junie CLI and the Junie plugin in JetBrains IDEs share one configuration: .junie/mcp/mcp.json in a project, ~/.junie/mcp/mcp.json for every project.

If it does not work in Junie

Junie cannot register or sign in
Turn on Let agents register themselves, with a base client, in the console under Authentication, then Agent readiness. Junie registers its own client the first time it connects.
Junie does not connect
A server marked Failed or Inactive: /mcp > Reconnect, or raise its timeout (milliseconds, 60 seconds by default).
Junie needs to sign in again
Run /mcp, choose the server, then Reconnect or Authorize.
Check your server the way Junie 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 Junie plan do your users need?

JetBrains' Junie MCP page does not name a plan.

Does my MCP server need to be public for Junie?

No. Junie 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 Junie 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