Products

Breno runs an MCP server and a REST API on the same personal tokens, so the AI tools you already use can search, read, ask and capture into what you keep.

What it does

01

One token, two doors

The same token works on the MCP endpoint and on the REST API. You choose its scopes and expiry, and you can revoke it at any time.

02

Same rules as the app

A token sees only what you can see. No model decides access.

03

Narrow on purpose

Anything outside the public operations refuses a token, so a leaked token cannot administer your workspace.

The screen

Nine tools

Search and fetch for plain lookups, ask for answers with citations, export, and capture notes and links.

A copy of the product, drawn with sample data.

  • searchread
  • fetchread
  • list_documentsread
  • read_documentread
  • list_sourcesread
  • ask_knowledgeask
  • export_knowledgeexport
  • capture_notewrite
  • capture_urlwrite

How it works

01

Create a token

Settings, then Connect AI. Name it, choose its scopes and expiry, and copy it once.

02

Add the server

Give your client the server URL and the token as a bearer header.

03

Use it

Search, fetch, ask, export and capture from inside the tool you already use.

What has been tested. The bearer-token route is the supported one. Adding Breno to Claude.ai or ChatGPT by URL with OAuth is built and tested with scripted clients, but has not yet been exercised against the live services.

Keep reading

MCP server

The endpoint, the nine tools and what has been tested.

Open

REST API

Personal tokens, scopes and seventeen operations.

Open

Ask

Answers with numbered citations, from your own material.

Open

Try it with your own material

Create a workspace, put a few real documents in, and ask it something you already know the answer to.

Create your account Contact us

Back to the home page