Brainstorm MCP
Remote MCP server exposing Brainstorm's Command Center reporting to Claude, GPT, and Cursor — scoped to whatever the signed-in staff user is allowed to see.
Endpoint
This server speaks MCP over Streamable HTTP at:
https://mcp-staging.brainstormtech.us/mcp
Every tool call runs as you — see Access below.
Connect a client
Org-wide already. In claude.ai: Settings › Connectors › turn on "Brainstorm MCP". Available in Claude Code too. First use opens a tab to sign in.
Org-wide already — shows up under MCP Tools in Cursor's settings. First use opens a tab to sign in.
Not pre-added. Settings › Connectors › Advanced › Add custom connector, paste the URL above. First use opens a tab to sign in.
What you can ask it
38 tools across 7 lanes, proxies into brainstorm-api — account_request_create creates records; the rest are read-only:
reporting_account_list: Accounts with SOW activity from the reporting martreporting_account_pulse: Pulse sentiment counts over unique accounts (command center)reporting_sow_people: List SOW people (leads + assignees) from the reporting martreporting_sow_list: List SOWs from the reporting martreporting_sow_summary: In-flight summary counts over active SOWs (command center)reporting_sow_pulse: Pulse sentiment counts over active SOWs (command center)reporting_sow_matrix: Project matrix points for active SOWs (timeline × burn pace)reporting_sow_managers: Distinct SOW project, account, design, QA, and scope owner leadsreporting_sow_tracked_time: Tracked time for many SOWs in one request (table views)reporting_sow_retainer_buckets: Retainer hour ledger for a SOWreporting_sow_payments: Payment schedule for a SOWreporting_sow_get: Get one SOW from the reporting mart by sow idreporting_sow_people_by_id: People (leads + assignees) for one SOWreporting_sow_tracked_time_by_id: Tracked time for a SOW, bucketed for charts and period totalsreporting_sow_milestone_items: List milestone line items for a SOW delivery milestonereporting_request_list: List accounts with non-billable request activity (reporting mart)reporting_request_summary: In-flight summary counts over active accounts (command center)reporting_request_tracked_time: Tracked time for many accounts in one request (table views)reporting_request_get: Get one account with its request items from the reporting martreporting_request_tracked_time_by_account: Tracked time for an account, bucketed for charts and period totals
reporting_search: Cross-entity picker search for reporting ids
reporting_timesheet_summary: Timesheet KPI summary for the filtered windowreporting_timesheet_nodes: Timesheet drill-down: next structure levelreporting_timesheet_people: Timesheet drill-down: who logged under a taskreporting_timesheet_entries: Timesheet drill-down: entry lines for one person
reporting_financial_summary: Invoicing, expenses, and payroll summary for a windowreporting_financial_revenue: Revenue buckets from QuickBooks invoices and paymentsreporting_financial_invoice: QuickBooks invoice list with linked SOWs (AR table)reporting_financial_payroll: Per-invoice payroll rows from the ClickUp Invoice Submission listreporting_financial_cost_breakdown: Per-user monthly labor cost matrix for one SOWreporting_financial_expense_summary: Grouped expense rollup (donut/table), payroll excludedreporting_financial_expense: QuickBooks expense transaction list
reporting_people_list: Team members with current-week billable sharereporting_people_summary: Team summary: billable utilization, bench, headcountreporting_people_capacity: Per-user capacity vs usage for a week or month (load graphs)reporting_people_get: One team member with week totals, tracked hours, and SOWs
account_request_create: Create account request
auth_context: Caller roles, dataScope, and permissions
Prompts
Two MCP Prompts wrap common multi-tool workflows:
- account_health_check
(accountId?): sweeps pulse sentiment and SOW risk signals (health/timeline/burn) for one account or the whole org, scoped to active SOWs plus anything completed in the last 30 days. - sow_status_report
(sowId): client-ready status report for one SOW: scope/timeline, budget burn, pulse, next milestone, payment status, risks. Keeps internal-only finance data out of the output.
account_health_check calls pulse two ways, and they render differently: reporting_account_pulse is wired to an interactive bar-chart widget (see Resources) that renders inline on MCP Apps-capable hosts, while reporting_sow_pulse has no widget and comes back as plain data. Same shape of question, two different rides.
Resources
- Reporting API enum glossary
glossary://reporting-enums: enum-valued query parameters (sort, groupBy, status, healthStatus, etc.) across every/reporting/*endpoint, keyed by (endpoint, method). Read this before guessing an enum value for areporting_*tool call. - Account pulse widget: interactive bar chart rendering
reporting_account_pulse(MCP Apps).
Access
This is an internal connector, not self-serve:
- Sign-in: only Brainstorm team members can connect, signing in with their Brainstorm email. If you can't log in, you don't currently have Command Center access.
- Authorization: what a tool returns depends on your role in Command Center — same as the web app. Finance data (revenue, payroll, cost) is only visible to roles with financial access; everyone else gets it redacted.