Skip to main content
The Brivvy Model Context Protocol (MCP) server lets AI assistants like Claude access your brand voice, content templates, audience definitions, and glossary terms directly. This means you can generate on-brand content right inside your AI tools. When connected, any MCP-compatible AI application can use Brivvy’s brand intelligence to create content that matches your voice and style guidelines. The server provides secure, authenticated access to your workspace through a standardized protocol. Brivvy’s MCP server is hosted and maintained by us, following the authenticated remote MCP specification. The available tools let you retrieve brand voice settings, access content templates, query audience definitions, and look up glossary terms. This ensures every piece of AI-generated content aligns with your brand standards.

​
General

The Brivvy MCP server supports the Streamable HTTP transport. Authentication uses OAuth 2.1 with dynamic client registration at: 
https://mcp.brivvy.io

​
Available tools

The Brivvy MCP server provides the following tools:
ResourceToolDescription
Voiceslist_voicesReturns all brand voices available in your workspace.
Voicesget_voiceRetrieves the full tone and style rules for a specific brand voice.
Templateslist_templatesReturns all content templates saved in your workspace.
Templatesget_templateRetrieves the generation prompt and instructions for a specific template.
Templateslist_discover_templatesBrowses publicly available templates from the Brivvy community.

​
Security and authentication

The Brivvy MCP Server uses OAuth authentication to connect with the Brivvy platform. Authentication tokens are stored locally on the device running the AI platform. No brand data is transmitted to AI platforms directly. The AI platform requests data from the MCP Server as needed during content generation. All requests require valid authentication.

​
FAQs

Clear your saved authentication data by running this in Terminal: rm -rf ~/.mcp-auth and try reconnecting. You may also need to update to a newer version of Node.js if prompted.
Try this alternative configuration:
{
  "mcpServers": {
    "brivvy": {
      "command": "wsl",
      "args": ["npx", "-y", "mcp-remote", "https://mcp.brivvy.io"]
    }
  }
}
The server accesses the workspace tied to your authentication credentials. If you have multiple workspaces, specify which one to use during OAuth or in your Brivvy account settings.