Boardroom Revenue Control

io.github.boardroomgen-ai-ae由 GitHub 帳號 boardroomgen-ai-ae 發布v1.0.0更新於 Oct 24, 2026

Read-only sales CRM for AI clients: leads, pipeline, AI-agent chats, calls, ad attribution.

已驗證Streamable HTTP可網頁執行溝通與協作資料與分析商業與電商

概覽

AI 產生的概覽

以唯讀方式透過 MCP 存取託管銷售 CRM：單一工作區的潛在客戶、銷售漏斗、AI 客服對話、通話、廣告歸因與行銷數據。

可以做什麼
檢視權杖身分、可讀工作區與權限範圍，並讀取工作區 KPI 快照與行銷快照（各活動的花費、觸及、點擊、每筆潛在客戶成本及 CRM 關聯），權杖允許時還可讀取合作夥伴後台數據。瀏覽潛在客戶清單、單筆潛在客戶記錄（含備註、事件、階段歷程與任務）、銷售漏斗各階段，以及依閒置時間排序、沒有未完成任務的潛在客戶。檢視 AI 客服對話的意圖、語言、訊息數與完整紀錄，以及客服設定，包括其知識文件標題。查看從廣告到對話及所綁定潛在客戶的歸因，並列出通話的方向、處理結果與通話時間。
適用情境
適合工作區擁有者希望助理在不開啟後台的情況下回答銷售跟進缺口、漏斗結構、客服對話、通話結果或廣告成效等問題。適用於已在使用 Revenue Control、透過對話成交的企業。
執行需求
遠端 streamable HTTP 端點，無需本機安裝套件。需要一個 Revenue Control 工作區，並在 Authorization 標頭提供 bearer 權杖，可由擁有者在 Integrations > API and MCP 中簽發，或透過擁有者核准的 OAuth 登入取得。需要能存取該託管服務的網路。
安裝前請注意
Authorization bearer 權杖可讀取單一工作區，且僅顯示一次，應妥善保存並在不再需要時撤銷。聯絡方式預設去識別化；完整電話、電子郵件與通訊軟體帳號需另行授予 crm:read_pii 權限。讀取操作會寫入工作區稽核日誌。公開 MCP 伺服器為唯讀，但同一平台的 REST API 包含寫入端點。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Boardroom Revenue Control，將其新增到工作區。
  2. 連接 Authorization token 憑證。它們會被私密儲存，絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.boardroomgen-ai-ae%2Fboro-ai/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "boardroom-revenue-control": {
      "type": "http",
      "url": "https://control.boardroom-ai.ae/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

Boro: your AI Business Operator

Revenue Control + Boro: an AI sales agent, CRM, booking and revenue dashboard for businesses that sell through conversations. Built by Boardroom AI, a global company headquartered in the UAE.

Boro does more than answer questions. It gets work done.

[License: Apache 2.0] [MCP: read tools live] [REST API: v1] [Languages: EN · RU · AR] [Built in Dubai] [Official MCP Registry] [Smithery] [Glama] [GitHub stars]

Start a free workspace · Website · Connect via MCP · REST examples · Русский

What it is

Revenue Control is a hosted, multi-tenant platform for businesses that sell through conversations: salons and clinics, real-estate agencies, education centres, service companies.

  • AI sales agent. It replies to customers on WhatsApp, Instagram, Telegram, website chat and voice, qualifies them, books appointments and hands over to a person when it should.
  • CRM. Pipelines, stages, tasks, notes and a full conversation history on every deal, filled in by the agent as it talks.
  • Booking. Slots, staff and reminders, plus connectors to the booking systems salons and clinics already use.
  • Revenue dashboard. Leads, conversion, follow-up gaps, ad spend against real deals, and revenue by source.
  • Boro. An operator inside the cabinet that reads all of the above and tells you what needs your attention today.

This repository is the public developer layer: documentation, connection guides and examples. The product itself runs as a cloud service at control.boardroom-ai.ae. The platform source code is not in this repository.

Connect Claude, ChatGPT or Cursor to your workspace in 3 minutes

Your workspace is also an MCP server. Any MCP client can read your leads, pipeline, AI-agent conversations, calls and marketing figures. Connect it in one of two ways.

One-click sign-in (OAuth). In a client that supports OAuth for remote MCP servers, such as a Claude custom connector or a ChatGPT connector in developer mode, add this URL:

https://control.boardroom-ai.ae/mcp/connect

The client opens the Revenue Control sign-in page. The workspace owner signs in and approves the connection on a consent screen. There is no token to copy: the client receives a read-only token, which appears in your token list in the cabinet and can be revoked there.

Owner-issued token. For Claude Code, Claude Desktop, Cursor, scripts and anything else that sends a header:

  1. Sign in to your workspace and open Integrations → API and MCP → Boardroom MCP → Get an MCP token. The token is shown once. Copy it.
  2. Add the server to your client:
bash
claude mcp add --transport http boardroom https://control.boardroom-ai.ae/mcp \  --header "Authorization: Bearer YOUR_MCP_TOKEN"
  1. Ask: "Which open leads have no follow-up task? Longest idle first."

Setup guides: Claude Code · Claude Desktop · Cursor · ChatGPT / OpenAI

Safe by design:

  • Read-only. The public MCP server has no write tools.
  • One workspace per token. The workspace comes from the token. A tool argument can never point at another tenant.
  • Masked by default. Lists and lead cards mask phone numbers and e-mails. Full contact details come back only for one specific record, and only if the owner granted the token that permission separately.
  • Audited. Every read is logged with the tool, the row counts and the record id. Response bodies and personal data are not stored in the log.
  • Owner-issued and revocable. Only the workspace owner can mint a token or approve an OAuth sign-in. Tokens expire, and you can revoke one at any time from the same card.

What you can ask

Ask your AI client or BoroStatus
"Find all leads that didn't receive a follow-up"Available now
"Show the funnel: how many deals and how much value per stage?"Available now
"Who wrote to us this week, in which language, and what did they want?"Available now
"Which ads produced conversations this month?"Available now
"How did calls go today: answered, missed, talk time?"Available now
"Tell me what requires my attention today" (Boro, in the cabinet)Available now
"Book a meeting tomorrow and move the deal" (Boro, in the cabinet)Beta: Boro prepares the action, you confirm it
"Summarise my inbox and draft replies" (Boro, in the cabinet)Beta: drafts only, never sends
The same write actions through MCP (note, task, stage, tags)Coming soon: preview-then-confirm
"Prepare quotations for customers waiting for prices"Coming soon

The 13 MCP tools are documented one by one in docs/mcp/tools.

REST API

A plain HTTPS API for your own systems, forms and automations:

bash
curl -s https://control.boardroom-ai.ae/api/v1/leads?limit=5 \  -H "Authorization: Bearer YOUR_API_KEY"

GET /api/v1/leads · GET /api/v1/deals · GET /api/v1/tasks · POST /api/v1/leads

Reference: docs/api/rest-v1.md. Examples in curl, JavaScript and Python, plus n8n and Make templates, are in examples/.

Works with

WhatsApp · Instagram · Telegram · Website chat · Voice · Kommo / amoCRM · Altegio · Zoho Books · Bayut / Property Finder · Meta, Google and TikTok Ads · any MCP client · n8n · Make

Some channels depend on approval by the channel provider for your business. The cabinet shows the honest status of each connection: Live, Needs setup, Draft or Unavailable.

How it works

 Customers                    Revenue Control (cloud)                      You ─────────                    ───────────────────────                      ─── WhatsApp  ┐                 ┌──────────────────────────┐ Instagram ├──► AI agent ───►│ CRM · booking · dashboard │◄── Boro (in the cabinet) Telegram  │   (replies,     │ one workspace per business│ Web chat  │    qualifies,   └─────────────┬─────────────┘ Voice     ┘    books)                     │                                           ├──► MCP server ──► Claude / ChatGPT / Cursor (read-only)                                           └──► REST /api/v1 ──► your forms, n8n, Make, scripts

Security

  • Every token and API key belongs to exactly one workspace. Requests never choose their tenant.
  • Credentials are stored as hashes. The plaintext is shown once, at creation.
  • OAuth sign-in uses the authorization code flow with PKCE (S256) and dynamic client registration. Only the workspace owner can approve it.
  • MCP is read-only. Actions in the cabinet go through an explicit confirmation step.
  • Every MCP read is written to the workspace audit log.
  • Rate limits apply to every token and every key.

Found a vulnerability? See SECURITY.md. Please don't open a public issue for it.

Roadmap

ItemStatus
✅MCP server, 13 read tools, owner-issued tokensAvailable now
✅One-click OAuth sign-in for Claude and ChatGPT connectorsAvailable now
✅Listings in the official MCP Registry, Smithery and GlamaAvailable now
✅REST API v1: leads, deals, tasks, create leadAvailable now
✅Website chat widgetAvailable now
🧪Boro actions in the cabinet (book, move stage, create task) with confirmationBeta
🧪Boro inbox digest and reply draftsBeta
🔜MCP write tools with preview-then-confirmComing soon
🔜MCP demo sandbox with a fictional CRM, no sign-up neededComing soon
🔜Listings in more client catalogsComing soon
💭Boro Skills: vertical packs for clinics, salons, real estateExploring

Want something on this list sooner? Open a feature request or ask for an integration.

Like it? Give it a star ⭐

A star helps other business owners and developers find a working MCP-to-CRM setup. If this repository saved you time, please star it.

Contributing

Doc fixes, new client guides and new examples are welcome. See CONTRIBUTING.md and the Code of Conduct.

License

Documentation and examples in this repository are licensed under Apache 2.0. "Boro", "Boardroom" and "Revenue Control" are names of Boardroom AI. The license covers this repository only, not the hosted service or its brand.

Boardroom AI, a global company headquartered in the UAE 🇦🇪 · control.boardroom-ai.ae

來源：README.md，提交 83047c7

工具

13

whoami

Who am I (token and workspace)

Who this token is, which workspace it can read, and which scopes it carries. Call this first: it tells you which of the other tools will work.

無需輸入參數。

crm_list_leads

List leads

Leads in this workspace, newest activity first. Phone and email are MASKED here — use crm_get_lead for one record when the full contact is genuinely needed. `total` is the count before paging, so it answers 'how many leads exist'. [scope: crm:read]

輸入參數limitsincestageoffsetpipeline_id

crm_get_lead

Get one lead

One lead — notes, events, stage history and open tasks. Phone, e-mail and messenger ids are MASKED unless this key also holds crm:read_pii, which the workspace owner grants separately. Scoped to this workspace: a lead id from elsewhere reads as not_found. [scope: crm:read]

輸入參數lead_id必填

crm_pipeline_overview

Pipeline overview

Every pipeline and stage with its lead count and total value. The shape of the funnel. [scope: crm:read]

無需輸入參數。

crm_leads_without_task

Leads without a follow-up task

Open leads with no unfinished task against them — the follow-up leak. Sorted by idle time, longest first. Idle days are counted in Asia/Dubai. [scope: crm:read]

輸入參數limit

ad_attribution

Ad attribution

Which advertisement produced which conversation: ad id, creative, first-touch flag, and the lead it bound to. The per-click id is NOT returned — only whether one exists. An empty result means no ad-driven conversation has been recorded in the window, not that the tool failed. [scope: marketing:read]

輸入參數limitsince

agent_conversations

AI-agent conversations

Conversations the AI agent handled, with intent, language, message count and the deal they bound to. Contacts masked. [scope: agent:read]

輸入參數limitsince

agent_get_conversation

One conversation transcript

One conversation with its transcript — what the customer wrote and what the agent answered. [scope: agent:read]

輸入參數limitconversation_id必填

dashboard_snapshot

Dashboard snapshot

The workspace's own KPI contract as the dashboard renders it, with the time it was built. [scope: crm:read]

無需輸入參數。

marketing_snapshot

Marketing snapshot

Advertising performance: spend, reach, clicks, cost per lead, per campaign, plus the CRM join. [scope: marketing:read]

無需輸入參數。

agent_config

AI-agent configuration

How the AI agent is set up for this workspace: mode and persona, working hours, hand-over rules, follow-up cadence, trigger list, actions, voice scenarios, and the TITLES of its knowledge documents. Document text is not returned — the list answers what the agent knows about; reading one whole is a separate, narrower ask. No credential of any kind is reachable from here: an agent's instructions are not its keys. [scope: agent:read]

無需輸入參數。

partner_overview

Partner overview

This partner's own cabinet: referral code and link, the clients who registered through it, the agreed commission rate, what has accrued so far, and which client workspaces this partner currently holds a grant for. Only answers for a token bound to a partner. [scope: partner:read]

無需輸入參數。

voice_calls

Voice calls

Calls with direction, disposition and talk time. Customer numbers masked. [scope: crm:read]

輸入參數limitsince

版本歷史

1
  1. v1.0.0最新Oct 9, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分