Connect a client

What to give an MCP client (a URL and a bearer token), the two ways to add Breno, and exactly what has and has not been tested against Claude.ai, ChatGPT and Cursor.

Report a problem with this page

Most MCP clients need two things from you: the server URL and a credential. The file or screen where you enter them differs from client to client, so follow your client's own instructions and give it these.

The two values#

The shape, not any one client's file

{
  "url": "https://<your-breno-host>/mcp",
  "headers": { "Authorization": "Bearer sirmx_mcp_…" }
}

Create the token in Connect AI. See Tokens.

Two ways to add Breno#

1. With a token (supported)#

Give the client the URL and the token as a bearer header, as above. This route works with any client that supports a remote MCP server with custom headers, and it is the one to use today.

2. By URL, with OAuth (built, not yet proven live)#

Some tools let you add a connector by URL alone and sign in through your browser. Breno supports OAuth 2.1 with dynamic client registration for that.

Clients that only speak stdio#

If your client can only start a local program, use the CLI bridge. See CLI.

After you connect#

Ask your tool something that needs your knowledge, for example "search Breno for our data retention policy". The tool calls search and fetch. If nothing comes back, see Troubleshooting.

What you are granting#

Whoever holds the token can do what its scopes allow, as you. Give a tool a token with only the scopes it needs, name it after the tool, and revoke it when you stop using it.