Brivvy Mcp
About
Connects AI assistants to your Brivvy workspace so they can use your brand voices, templates, and glossary for on-brand content—hosted at mcp.brivvy.io.
Details
- Author
- brivvyHQ
- Downloads
- 292
- Categories
- Productivity, Other, Marketing, Automation
Jump to
- 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.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Brivvy McpCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
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.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"brivvy mcp": {
"Brivvy": {
"url": "https://mcp.brivvy.io"
}
}
}
}McpServers
{
"Brivvy": {
"url": "https://mcp.brivvy.io"
}
}This repo is your public entry point for Brivvy AI integrations. You get MCP server metadata, install steps, client connection profiles, and release notes.
The implementation stays private. Everything here is safe to publish.
- Server type:Remote MCP (Streamable HTTP).
- Production URL:https://mcp.brivvy.io.
- Auth:OAuth 2.1-style flow with PKCE.
- Discovery:Use these before you call the JSON-RPC endpoint:
- https://mcp.brivvy.io/.well-known/oauth-protected-resource.
- https://mcp.brivvy.io/.well-known/oauth-authorization-server.
These tool names are the public contract. Short descriptions match what the hosted server exposes today (seeMCP Serverfor connection guides, security notes, and FAQs).
{ "mcpServers": { "Brivvy": { "url": "https://mcp.brivvy.io" } } }
Connect once, then finish OAuth in the browser when the client asks you to.
- URL:https://mcp.brivvy.io.
- Transport:Streamable HTTP.
- Auth:OAuth.
Claude reads.well-knownmetadata and walks you through consent.
Your Brivvy account usesone workspace at a timefor MCP. The workspace youlast pickedon the OAuth screen applies toeveryMCP client until you authorize again and choose a different one. If you run Cursor and Claude side by side, they do not keep separate workspace picks today.
Your access token stays short-lived. The client should refresh it with your refresh token. Refresh tokens last90 days(Amazon Cognito). When that window ends, connect again and run through OAuth.
- 401onPOST /:Normal before OAuth. Your client should follow theWWW-Authenticatehint and complete discovery.
- Disconnects right after consent:Check the callback URL, try once more, and make sure you finished the OAuth popup.
- Token errors:Reconnect so you get a fresh bearer token. Do not reuse an old web session token.
- No tools listed:Your MCP consent or workspace access may be missing or expired.
- Wrong workspace:Reconnect and pick the workspace you want on the OAuth screen. That choice applies across all MCP clients on your account.
- mcp/server.json, registry metadata.
- mcp/install/, Cursor and Claude profiles.
- VERSIONING.md, how we version this public metadata.
- CHANGELOG.md, release notes.
- SECURITY.md, how to report issues.
Internal release and directory workflows stay in the private Brivvy MCP repo.
- Support:support@brivvy.io.
- Security:security@brivvy.io.
Create, schedule, and publish LinkedIn posts directly from Claude Desktop or ChatGPT through natural conversations
Automate Ghost CMS with full CRUD operations, bulk actions, and advanced features.
An AI-native publishing engine for persona-driven content creation and multi-platform publishing.
A suite of tools for technical marketing content creation, optimization, and product positioning based on Open Strategy Partners' methodologies.
his server allows AI assistants (like Claude) to manage your social media content.
Connect AI agents to project data, analytics, research, content planning, media generation, and growth workflows.
Connect AI tools like Claude, Cursor, and Codex directly to your CitedSpy workspace with the Model Context Protocol (MCP). Once connected, your AI assistant can read your brands, prompts, runs, citations, and analytics - and create prompts or trigger runs - without you copying data back and forth. You can ask for your AI visibility dashboard in plain language, find your weakest prompts and engines, create and edit tracking prompts from chat, trigger fresh runs across engines, pull citations, mentions, and reports into your AI workflow
MCP server that distributes a single piece of content across 8+ channels (DEV.to, Hashnode, GitHub Discussions, Reddit, Bluesky, LinkedIn, Medium, Twitter) with automatic platform-specific adaptation, idempotent publishing, per-community anti-spam rules, and centralized state management.
Publish, schedule, moderate your social inbox, and pull analytics across every major network directly from any AI assistant, via Eclincher.
Run reusable AI creative workflows for ecommerce product photography, UGC ads, image-to-video, text-to-video, asset uploads, and async generation results.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
