What transport does Brivvy Mcp use?
Brivvy Mcp runs over Streamable HTTP at `https://mcp.brivvy.io`.
@brivvyHQ
Basic information
Give AI assistants your Brivvy brand voices, templates, and glossary so generated content matches your team’s standards.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"Brivvy": {
"url": "https://mcp.brivvy.io"
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
Fetch the live tool list directly from this server's endpoint using the button above.
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.
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.
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.Brivvy Mcp runs over Streamable HTTP at `https://mcp.brivvy.io`.
OAuth with PKCE is used. After browser-based consent, one workspace selection applies across MCP clients until you explicitly re-authorize.
It exposes three categories: voices (brand voices and tone rules), templates (workspace and public catalog), and glossary (terminology and guidance).
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`.
Email `support@brivvy.io` for general support or `security@brivvy.io` for security issues. See the repository’s `SECURITY.md` for details.
Open-source MCP to use Blender with any LLM

Model Context Protocol Servers
🚀 The fast, Pythonic way to build MCP servers and clients.

See and control a real Windows PC you own — from any MCP client, locally or remotely. Observe (UIA + screenshots), click/type/drag/scroll, launch apps, owner Live View. BYOH: your machine, your key.

Model Context Protocol Servers
Comments