Read-only sales CRM for AI clients: leads, pipeline, AI-agent chats, calls, ad attribution.
Connect Remote server
claude mcp add --transport http boro-ai https://control.boardroom-ai.ae/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"boro-ai": {
"url": "https://control.boardroom-ai.ae/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"boro-ai": {
"type": "http",
"url": "https://control.boardroom-ai.ae/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://control.boardroom-ai.ae/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 13 found in our last check
whoamiWho 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_leadsLeads 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_leadOne 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_pipeline_overviewEvery pipeline and stage with its lead count and total value. The shape of the funnel. [scope: crm:read]
crm_leads_without_taskOpen 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_attributionWhich 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. [s…
agent_conversationsConversations the AI agent handled, with intent, language, message count and the deal they bound to. Contacts masked. [scope: agent:read]
agent_get_conversationOne conversation with its transcript — what the customer wrote and what the agent answered. [scope: agent:read]
dashboard_snapshotThe workspace's own KPI contract as the dashboard renders it, with the time it was built. [scope: crm:read]
marketing_snapshotAdvertising performance: spend, reach, clicks, cost per lead, per campaign, plus the CRM join. [scope: marketing:read]
agent_configHow 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; rea…
partner_overviewThis 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_callsCalls with direction, disposition and talk time. Customer numbers masked. [scope: crm:read]
Headers
| Name | Description |
|---|---|
AuthorizationRequired, secret | Bearer <token>. The workspace owner issues and revokes it in Integrations > API and MCP. |
Details
| Endpoint | https://control.boardroom-ai.ae/mcp (Streamable HTTP) |
| First published | 9 Oct 2026 |
| Last updated | 9 Oct 2026 |
| Registry name | io.github.boardroomgen-ai-ae/boro-ai |
More marketing and seo servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
