API Tools

boardroom-ai.ae

An MCP server that exposes a CRM workspace API, letting agents inspect tokens, list and retrieve leads, view pipeline stages, and find open leads missing follow-up tasks.

1 endpoint13 known toolsFirst detected October 10, 2026Last detected October 10, 2026

ENDPOINT 1

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

No auth detected

MCP server metadata

Name: boardroom-control-revenue
Version: 1.0.0

Capabilities

tools

Server instructions

Read-only access to one Revenue Control workspace (sales CRM, AI-agent conversations, calls, ads). Call whoami first: it names the workspace and which tools this token may use. Lists mask phone numbers and e-mails; use crm_get_lead only when one full record is genuinely needed. Times are Asia/Dubai.

Known tools 13

whoami

Who this token is, which workspace it can read, and which scopes it carries.

Inferred read-only

crm_list_leads

Leads in this workspace, newest activity first.

Inferred read-only

crm_get_lead

One lead in full — unmasked contact details, notes, events, stage history and open tasks.

Inferred read-only

crm_pipeline_overview

Every pipeline and stage with its lead count and total value.

Inferred read-only

crm_leads_without_task

Open leads with no unfinished task against them — the follow-up leak.

Inferred read-only

ad_attribution

Which advertisement produced which conversation: ad id, creative, first-touch flag, and the lead it bound to.

Inferred read-only

agent_conversations

Conversations the AI agent handled, with intent, language, message count and the deal they bound to.

Potential side effects

agent_get_conversation

One conversation with its transcript — what the customer wrote and what the agent answered.

Inferred read-only

dashboard_snapshot

The workspace's own KPI contract as the dashboard renders it, with the time it was built.

Inferred read-only

marketing_snapshot

Advertising performance: spend, reach, clicks, cost per lead, per campaign, plus the CRM join.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

voice_calls

Calls with direction, disposition and talk time.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.boardroom-control-revenue]
url = "https://control.boardroom-ai.ae/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "boardroom-control-revenue": {
      "type": "http",
      "url": "https://control.boardroom-ai.ae/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: boardroom-control-revenue
Remote MCP URL: https://control.boardroom-ai.ae/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "boardroom-control-revenue": {
      "url": "https://control.boardroom-ai.ae/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "boardroom-control-revenue": {
      "type": "http",
      "url": "https://control.boardroom-ai.ae/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "boardroom-control-revenue",
  "transport": "streamable-http",
  "url": "https://control.boardroom-ai.ae/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for boardroom-ai.ae was fetched 2026-10-11T12:16:27.854Z.

Trust status Neutral

boardroom-ai.ae is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.