Boardroom Revenue Control is answering right now. Last checked 4 min ago. It exposes 13 tools. Last commit 12 Oct 2026.
Read-only sales CRM for AI clients: leads, pipeline, AI-agent chats, calls, ad attribution.
Uptime history
7 days of history
7 days agonow
100.0%
Uptime 24h
92 of 92 checks
13
Tools
read from the server
1552 ms
Response time
average over 24h
0
Stars
last commit 12 Oct 2026
What changed 4
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 October 2026. No other catalogue keeps this.
11 Oct
3 tools changed the parameters they ask for
agent_get_conversation, crm_get_lead, crm_list_leads
11 Oct
a tool description was rewritten
crm_get_lead
Nothing serious here today
Today is the operative word: we check Boardroom Revenue Control every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.
run in your terminal
claude mcp add boro-ai --transport http https://control.boardroom-ai.ae/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"boro-ai": {
"url": "https://control.boardroom-ai.ae/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.boro-ai]
url = "https://control.boardroom-ai.ae/mcp".cursor/mcp.json
{
"mcpServers": {
"boro-ai": {
"url": "https://control.boardroom-ai.ae/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"boro-ai": {
"url": "https://control.boardroom-ai.ae/mcp"
}
}
}Available tools 13
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
crm
crm_get_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]
crm_leads_without_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]
crm_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]
crm_pipeline_overview
Every pipeline and stage with its lead count and total value. The shape of the funnel. [scope: crm:read]
agent
agent_config
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]
agent_conversations
Conversations the AI agent handled, with intent, language, message count and the deal they bound to. Contacts masked. [scope: agent:read]
agent_get_conversation
One conversation with its transcript — what the customer wrote and what the agent answered. [scope: agent:read]
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]
dashboard
dashboard_snapshot
The workspace's own KPI contract as the dashboard renders it, with the time it was built. [scope: crm:read]
marketing
marketing_snapshot
Advertising performance: spend, reach, clicks, cost per lead, per campaign, plus the CRM join. [scope: marketing:read]
partner
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
voice_calls
Calls with direction, disposition and talk time. Customer numbers masked. [scope: crm:read]
whoami
whoami
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://control.boardroom-ai.ae/mcp | streamable-http | answering | 1333 ms | 4 min ago |
Alternatives to Boardroom Revenue Control
same job, measured the same wayChatflow
by yersat
WhatsApp CRM for AI agents: search contacts, read chats, manage the sales pipeline, send messages.
Salesforce Marketing
by zleventer
MCP server for Salesforce — 47 tools for leads, campaigns, pipeline, attribution, and reporting.
D
DNAAI prediction ledger
by dnaai
Read-only ledger of agent forecasts: events, rules, leaderboard, calibration.
Kordic CRM
by meelad-diggit
CRM integration for leads, pipeline, contacts, accounts, payments, and sales analytics.
MintwareDevelopers
by mintwaredevelopers
Look up on-chain Attribution reputation scores for wallets and AI agents on Base.
Sellinger CRM
by sellinger
Manage Sellinger AI SDR CRM leads, conversations and pipeline from any MCP client.
Brevet
by brightbeamai
Change control for what AI agents learn: humans promote, releases are signed, rules can be recalled
MCP Android
by dockndevai
Control Android devices over ADB from AI agents — safe-by-default, read-only by default, audited.
Boardroom Revenue Control — questions
Answers built from our own checks of this server.
What can Boardroom Revenue Control do?
It exposes 13 tools, read directly from the server on our last check. Among them: ad_attribution, agent_config, agent_conversations, agent_get_conversation, crm_get_lead, crm_leads_without_task and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Boardroom Revenue Control mostly used for?
Its tools cluster around crm and agent. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Boardroom Revenue Control working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 1552 ms. The bar chart above shows every period we have measured.
How do I connect Boardroom Revenue Control?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Boardroom Revenue Control need an API key?
No. Boardroom Revenue Control completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Boardroom Revenue Control?
It answers our handshake in 1552 ms on average, which is faster than 3% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Boardroom Revenue Control open source?
Yes — it is published under the Apache-2.0 licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.