Boardroom Revenue Control

Name: Boardroom Revenue Control
Author: boardroom-gen

Read-only MCP server for a sales CRM built for SMBs in the UAE and CIS.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

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.
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
Crm Get Lead: One lead in full — unmasked contact details, notes, events, stage history and open tasks. Scoped to this workspace: a lead id from elsewhere reads as not_found. [scope: crm:read]

What data it sees

Do you need an account

No: the server works without sign-in

Read-only MCP server for a sales CRM built for SMBs in the UAE and CIS. Ask Claude or Cursor about your leads, pipeline, AI-agent conversations (WhatsApp, Instagram, Telegram, web chat, voice), calls and ad attribution. One token per workspace, issued and revoked by the owner; phone numbers and e-mails are masked in lists. Docs: https://github.com/boardroomgen-ai-ae/boro-ai

How to connect

How to connect Boardroom Revenue Control to Claude

The server address to paste into Claude settings:

https://revenue-control--boardroom-gen.run.tools

Open Claude (claude.ai or the desktop app).
Go to Settings → Connectors.
Click Add custom connector.
Paste the server address copied below into Remote MCP server URL and click Add.
In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Boardroom Revenue Control to ChatGPT

The server address to paste into ChatGPT settings:

https://revenue-control--boardroom-gen.run.tools

Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
Open Settings → Connectors and click Create.
Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Boardroom Revenue Control to Cursor

The server address to paste into Cursor settings:

https://revenue-control--boardroom-gen.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (13)

Raw names from tools/list. Only developers need these.

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.
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_get_lead	One lead in full — unmasked contact details, notes, events, stage history and open tasks. Scoped to this workspace: a lead id from elsewhere reads as not_found. [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]
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]
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]
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]
dashboard_snapshot	The workspace's own KPI contract as the dashboard renders it, with the time it was built. [scope: crm:read]
marketing_snapshot	Advertising performance: spend, reach, clicks, cost per lead, per campaign, plus the CRM join. [scope: marketing:read]
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]
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	Calls with direction, disposition and talk time. Customer numbers masked. [scope: crm:read]