Brivvy Mcp

What is Brivvy Mcp?

Brivvy Mcp is the hosted Model Context Protocol surface for Brivvy. It runs over Streamable HTTP at https://mcp.brivvy.io and uses OAuth with PKCE for browser-based consent.

How to use Brivvy Mcp?

Connect via Streamable HTTP at https://mcp.brivvy.io using OAuth with PKCE. Once authorized, one OAuth workspace selection applies across MCP clients until you re-authorize. Full product documentation is available at https://docs.brivvy.io/mcp-server.

Key features of Brivvy Mcp

• list_voices and get_voice for brand voices and tone/style rules.
• list_templates, list_discover_templates, and get_template for workspace and public catalog templates.
• Glossary surface terminology and guidance via voice context.
• OAuth workspace selection persists across MCP clients.
• Well-known endpoints for OAuth discovery on the same host.

Use cases of Brivvy Mcp

• Retrieve published brand voices for consistent tone in content generation.
• Access workspace templates and the public template catalog for reuse.
• Incorporate glossary terminology and guidance into AI-assisted writing.
• Manage voice and template resources across a Brivvy workspace.

FAQ from Brivvy Mcp

What transport does Brivvy Mcp use?

Brivvy Mcp runs over Streamable HTTP at https://mcp.brivvy.io.

How does OAuth authentication work?

OAuth with PKCE is used. After browser-based consent, one workspace selection applies across MCP clients until you explicitly re-authorize.

What data can Brivvy Mcp access?

It exposes three categories: voices (brand voices and tone rules), templates (workspace and public catalog), and glossary (terminology and guidance).

Where can I find documentation and versioning?

Product docs are at https://docs.brivvy.io/mcp-server. The public manifest and changelog are in the GitHub repository brivvyHQ/ai under mcp/server.json.

How do I get support?

Email [email protected] for general support or [email protected] for security issues. See the repository’s SECURITY.md for details.