The voice rules and the actual prompt behind a saved template are fetched from Brivvy at the moment of writing, so a draft starts from the same rules your team edits in the product rather than from a copy someone pasted months ago.
A remote MCP server at https://mcp.brivvy.io, connected over Streamable HTTP with OAuth. Five read tools expose one Brivvy workspace: its published voices, the tone and style rules behind them, its saved templates, and the public community catalogue.
- The published voices in your workspace
- The tone and style rules for the default voice, or for one you name
- The content templates saved in your workspace
- Public templates from the Brivvy community catalogue
- The full prompt and instructions behind a template you pick
A Brivvy account, authorized over an OAuth flow with PKCE. One workspace applies at a time: the workspace picked last on the consent screen is the one every MCP client sees until you authorize again. Refresh tokens expire, after which you reconnect.
One command — npx -y mcp-remote https://mcp.brivvy.io