Connect AI tools
Use what Breno keeps from Claude, ChatGPT, Cursor and your own scripts, over MCP or the REST API, with one personal token and the same access rules as the app.
Breno has two doors for tools and code, and one token opens both.
| MCP server | REST API | |
|---|---|---|
| For | AI tools that speak the Model Context Protocol (Claude, ChatGPT, Cursor, and others) | Your own scripts and programs |
| Endpoint | /mcp on your Breno host | /api/v1 |
| What it offers | Nine tools and document resources | Seventeen operations |
| Credential | A personal token, as Authorization: Bearer sirmx_mcp_… | The same token |
What stays the same everywhere#
- A token is you, in one workspace. It sees what you can see: the spaces you belong to, the sensitivity labels you are cleared for, and your own private items. Nothing gives a token more than its owner has.
- Scopes narrow it. You choose
read,ask,exportandwritewhen you create it. - It dies with your access. It stops working at once when you revoke it, when it expires, when you leave the workspace, when your account is erased, or when the workspace is deleted.
- It is audited. Uploads, captures, note edits and exports made with a token are recorded in the workspace audit log, with the token's id.
- It is narrow on purpose. Anything outside the public operations (deleting, sharing, members, settings, token management, connecting sources) refuses a token, so a leaked token cannot administer your workspace.
Choose your way in#
TokensCreate one, choose scopes, and revoke it.MCP serverThe endpoint, the nine tools and the resources.Connect a clientWhat to give your AI tool, and what has been tested.CLIBridge a client that only speaks stdio.REST APIFor your own code.
An honest note about status#
The bearer-token route is the supported one. The OAuth flow that lets you add Breno to Claude.ai or ChatGPT by URL is built and tested with scripted clients, but has not yet been exercised against the live services. See Connect a client.