
Brivvy MCP
io.github.brivvyHQ由 GitHub 帳號 brivvyHQ 發布v0.1.0更新於 Oct 24, 2026
Brivvy MCP (OAuth): on-brand AI content, voice rules, templates, glossary.
概覽
Brivvy MCP 是需要 OAuth 授權的遠端伺服器,讓助理存取你 Brivvy 工作區的品牌語氣、語調規則與內容範本。
- 可以做什麼
- 列出工作區中已發布的語氣(voices),並讀取預設或指定語氣的語調與風格規則。列出工作區儲存的內容範本,並取得所選範本的完整提示詞與說明。瀏覽 Brivvy 社群目錄中的公開範本。伺服器只提供這些查詢類能力,未列出內容生成工具。
- 適用情境
- 適合希望助理以一致的品牌語氣撰寫或改寫內容,或把已儲存的範本與社群範本直接帶入寫作流程、省去手動複製提示詞的情況。
- 執行需求
- 透過網路存取的遠端 Streamable HTTP 端點,不需本機安裝套件。需要具備工作區存取權限的 Brivvy 帳號,並在瀏覽器中完成 OAuth 登入(PKCE 流程,透過 well-known 中繼資料探索)。存取權杖有效期短,需以有效期 90 天的更新權杖續期。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Brivvy MCP,將其新增到工作區。
- 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.brivvyHQ%2Fmcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。
{
"mcpServers": {
"brivvy": {
"type": "http",
"url": "https://mcp.brivvy.io/"
}
}
}README
Brivvy AI
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.
What you connect to
- 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.
Tools you can rely on
These tool names are the public contract. Short descriptions match what the hosted server exposes today (see MCP Server for connection guides, security notes, and FAQs).
Quick start
Cursor
Add Brivvy as a remote MCP server:
Connect once, then finish OAuth in the browser when the client asks you to.
Claude
Point your MCP connector at:
- URL:
https://mcp.brivvy.io. - Transport: Streamable HTTP.
- Auth: OAuth.
Claude reads .well-known metadata and walks you through consent.
Workspace scope
Your Brivvy account uses one workspace at a time for MCP. The workspace you last picked on the OAuth screen applies to every MCP 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.
Sessions and reconnection
Your access token stays short-lived. The client should refresh it with your refresh token. Refresh tokens last 90 days (Amazon Cognito). When that window ends, connect again and run through OAuth.
When something breaks
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.
What lives here
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.
How to reach us
- Support:
[email protected]. - Security:
[email protected].
來源:README.md,提交 f864d99
工具
0版本歷史
1- v0.1.0最新Sep 16, 2026
評分
已滿足適用檢查項的 85%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分