Every agent knows what your team knows.
Brewale shares your team's conventions and reusable skills with every AI agent — over one connection where you decide, tool by tool, what they're allowed to touch.
14-day free trial, no card. The clock only starts on your org's first MCP request.
Every agent is set up a little differently
Connect an MCP server and your agent gets every tool it exposes — delete endpoints sitting right next to read endpoints.
Credentials end up in config files, one per agent, per laptop. Offboard someone and you're hunting tokens.
And every repo carries its own CLAUDE.md, all slightly out of date, all slightly disagreeing.
That's fine for one person. It's not fine for a team.
Three things, one connection
You manage them in Brewale. Your agents read them over MCP.
Conventions
One document your agents actually follow.
Write your standards once, in markdown. Every connected agent reads the published version — no per-repo copies drifting apart.
Skills
Reusable instructions, versioned like code.
Package a recurring task as a skill and any agent can load it on demand. Author them from your agent or sync them from your own GitHub repo.
Tool access
Your MCP servers, on your terms.
Connect any MCP server and decide tool by tool what agents may call — read, write, or delete. Revoke in a click.
How it works
Set it up
Bring in your conventions and skills as markdown — drafted by your agents over MCP, or synced from your GitHub repo — and connect the MCP servers your team already uses.
Decide who gets what
Switch each tool on or off, mark it read, write, or delete, and set org defaults or per-member limits.
Point your agents at Brewale
One command, one connection. Everything you publish reaches every agent within about 5 seconds.
$ npx brewale
One setup, the whole team
Per-seat pricing, everything included. Sign in with OAuth or an API key, revoke access in a click, and take your markdown with you if you ever leave.