Bonnard
Get started

Apps

Install a Bonnard app in your AI client

Updated

To get charts from your database in Claude, ChatGPT or another AI client, add a Bonnard app to the client as a connector and sign in. The client then draws the charts in the conversation.

The console at app.bonnard.ai has install links for Claude, ChatGPT, and Cursor. Other clients take the app’s URL. To create an app first, follow the Quickstart.

Find the install menu

  1. In the console, open Apps, then your app.
  2. On the Overview tab, the Endpoints card lists Production, the URL to share, and Staging, for testing by members of your workspace.
  3. Select the arrow next to a URL (More install options).

Production’s install links work once the app is published.

Get charts in Claude

  1. Select Install in Claude. Claude opens its Add custom connector dialog in a new tab, with the app’s name and URL filled in.
  2. Confirm the dialog, sign in to Bonnard, and select Authorize.
  3. Ask for a chart, naming the app.

The link adds the app to your Claude account only.

Get charts in ChatGPT

ChatGPT’s link cannot carry the URL, so copy it first.

  1. In the install menu, select Copy URL, then Install in ChatGPT. ChatGPT opens its new connector dialog in a new tab.
  2. Paste the URL, complete the dialog, sign in to Bonnard, and select Authorize.
  3. Ask for a chart, naming the app.

Get charts in Cursor

  1. Select Install in Cursor and let your browser open Cursor.
  2. Confirm Cursor’s install prompt, sign in to Bonnard, and select Authorize.

Use the app in Codex

Add the app’s production URL to Codex as a remote MCP server. Codex gets each chart’s data and settings, but draws no chart.

Get charts in other AI clients

Gemini, Langdock, Goose, Mistral, Archestra, Glean, Microsoft Copilot, and other clients take the production URL as a custom connector or remote MCP server. To show charts, a client must render MCP apps and support:

  • MCP over Streamable HTTP, with POST requests only.
  • MCP authorization (OAuth 2.1 with PKCE). The client reads the sign-in details from the app’s URL and registers itself, so there is no client ID to set up.

What sign-in asks for

Connecting opens Bonnard’s sign-in page. Members of your workspace sign in with their Bonnard account. Your customers’ users enter their work email and the 6-digit code sent to it, or use their company’s single sign-on if you set it up.

Authorize access then names the client and what it can do. Select Authorize or Deny.

Verified origin names the host the client proved it comes from, such as claude.ai. With Unverified identity, check where the page says it will send you.

Someone in more than one of your customers first picks one under Which organization?.

Connect a script with an API key

A script or agent that cannot sign in through a browser sends an API key in an Authorization: Bearer <key> header.

  • For an app with the Internal or All customers audience on a No tenancy database, select Generate API key on the app’s Settings tab. The key works for that app only.
  • For other apps, create a customer user’s key: on Customers, open the customer, then API keys in the user’s row menu.

Copy the key when it appears: Bonnard shows it once.

If the connection fails

Connection errors and what to do
MessageWhat to do
MCP server '<slug>' is not live.Publish the app.
This MCP server is not available to you.Add the person, or their customer, to the app’s audience.
Staging is available to console admins only.Use the production URL.
This authorization request has expired or is no longer valid.Start again from the AI client.

MCP errors carry a request ID starting bnreq_: quote it when you ask for help.