BUCS Analytics (Preview)

BUCS Analytics connects an AI assistant to your live accounting and financial data in BUCS, so you can ask plain-language questions and get answers traced to the underlying ledger: cash position and runway, AR and AP aging, trial balance, EBITDA, revenue and expense breakdowns, working capital, reconciliation status, and dozens of related metrics. Access is read-only, scoped to one company per connection, and fully audited. No data is created or changed.

This connector is available in the following products and regions:

BUCS Analytics MCP Server

The BUCS Analytics MCP server gives an AI assistant secure, read-only access to a company's accounting and financial data managed in BUCS — so you can ask natural-language questions like "What do customers owe us past 90 days?" or "What's our cash position and runway?" and get answers traced to the underlying ledger.

What it does

Once connected and authorized for a company, the assistant can call BUCS analytics tools covering:

• Receivables & payables — AR/AP aging (summary and by-customer/vendor), AR/AP concentration, DSO/DPO, cash conversion cycle.
• Liquidity — cash position, runway, working capital.
• Profitability — revenue trend/growth, revenue and expense breakdowns, gross-profit decomposition, EBITDA and adjustments, operating leverage, financial ratios.
• Close & integrity — reconciliation status, close items/KPIs, GL anomalies, signal flags.
• Detail & discovery — transactions search, account balances, top customers/vendors, dataset and metric discovery (list_datasets, describe_dataset, describe_metric).

All tools are read-only — the server exposes no write/create/update/delete operations. Every tool is annotated readOnlyHint: true.

Authentication

The server supports two methods:

1. OAuth 2.0 (recommended) — "Connect with BUCS". The server supports OAuth 2.0 Dynamic Client Registration with discovery (RFC 8414 / 7591 / 9728, PKCE), so clients can self-register and discover endpoints automatically. During sign-in you choose the company and the datasets the connection may read; consent is recorded for audit.
2. API key — a BUCS Data Gateway key passed in the X-Api-Key header. Keys are firm-scoped and may be further restricted to a single company and an allowlist of datasets.

Setup

1. Add the MCP server using your client's connector flow with the server URL (the BUCS API host, path /api/mcp).
2. Choose OAuth 2.0 → Dynamic discovery (or supply an API key).
3. Sign in and grant access to the company and datasets you want the assistant to read.

Transport

Streamable HTTP (MCP). SSE is not supported.

Data handling & privacy

• Access is scoped to one firm, and to a single company per connection (and optionally a dataset allowlist). Cross-company/cross-firm access is rejected.
• Every tool call is logged for audit (caller, company, tool, timing) under BUCS's SOC 1 controls.
• The assistant only ever receives the data returned by the read-only tools you authorized.
• Privacy policy: https://bucsanalytics.com/privacy-policy/ (confirmed 2026-06-30 — BUCS's existing corporate policy).

Known limitations

• Read-only — no data is created or modified through this connector.
• One company per connection — to query a different company, authorize a separate connection (or supply companyId on a firm-wide API key).
• Period is an as-of filter — period-keyed tools compute a view of the company's canonical data as of the requested period; they do not read separate per-period snapshots.
• A dataset-restricted key can only call tools whose underlying datasets are all within its allowlist.

Support

• Support: https://bucs.teamwork.com/support/#/tickets/new or support@bucsanalytics.com (any email creates a ticket in the same queue). Response time: 24 hours or less. (confirmed 2026-06-30)

Actions

BUCS MCP