Reconnecting...
Trying to restore the connection
Reconnecting...
Trying to restore the connection
Brila speaks the Model Context Protocol, so Claude, Cursor or any MCP client can read your account and answer in plain language. The REST API covers the rest — your profile, links, codes, automations and statistics — with the same token. Both are on every plan, including the free one.
MCP server
Add Brila to your AI client once, with a token you create in Settings. From then on your discount codes are something you can simply ask about — which ones are live, which expire this week, what that code you saved last month was.
Public API
Personal access tokens over a documented OpenAPI surface. Reads and writes both: publish a discount code, reorder your links, update your bio, pull yesterday's statistics.
Settings → API Tokens. Choose what it may reach, and copy it once — Brila stores only a hash.
One command in Claude Code, or a few lines of JSON in Claude Desktop and Cursor. The docs carry both.
“Which of my codes expire this week?” Your client calls Brila and answers from your own rows.
The API and the MCP server are on every plan, the free one included. Your calls are not metered.
One per machine, script or client, so a credential that leaks costs you one of them rather than all of them.
The usage endpoint reports every quota on your account and how much of it you have spent.
Create a free account, make a token, and connect your assistant.
Get started