Monte Carlo (BYOK)

Monte Carlo (BYOK) — connector documentation

• MCP endpoint: https://byok-monte-carlo.connectorbay.com/mcp
• REST API: POST https://byok-monte-carlo.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-monte-carlo.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Monte Carlo Monte Carlo API token, sent in the X-Upstream-Key header and the Monte Carlo API key ID in X-Upstream-Key-2 of every request (never stored, logged or cached)
• Health: https://byok-monte-carlo.connectorbay.com/health · Tool schemas: https://byok-monte-carlo.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-monte-carlo · agent@connectorbay.com

What Monte Carlo (BYOK) is for

Monte Carlo (BYOK) lets an AI assistant read your own Monte Carlo data through the Monte Carlo API with a key you supply (Monte Carlo API token). Read-only: 8 tools (get_current_user, list_domains, list_data_products, list_tables, get_table, list_alerts, list_monitors, list_account_roles). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.getmontecarlo.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Monte Carlo. Monte Carlo and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which Monte Carlo account does my API key belong to?"
• "Which domains are set up in Monte Carlo?"
• "Which data products exist in Monte Carlo?"
• "Which tables in Monte Carlo are tracked and what is their status?"
• "Show Monte Carlo details of table MCON++1++2++table++db:public.orders"
• "Which Monte Carlo alerts were raised in the last two weeks?"

What it does

• get_current_user: Show the Monte Carlo user or service account that owns the key: id, display name, state, role, SSO flag and creation time.
• list_domains: List Monte Carlo domains (groups of assets owned by a team) with name, description, type and tag.
• list_data_products: List data products with name, description, creation and update time, optionally within one domain.
• list_tables: List tables and views that Monte Carlo has discovered, with type, location, tracked and muted flags, status, priority and last observed and modified times. Cursor paginated.
• get_table: Get one table by MCON: type, location, description, tracked and muted flags, status, priority, anomaly flags, schema change count and timestamps.
• list_alerts: List alerts (grouped incidents) created within a time window of at most two months, with title, type, status, severity, comment count and URL. This API field is marked experimental by the vendor. Cursor paginated.
• list_monitors: List monitors (data quality checks) with type, name, description, severity, schedule, paused and snoozed flags, status, next and previous run times and recent incident count.
• list_account_roles: List the authorization roles of the account with name, label, description, version and whether Monte Carlo manages the role.

BYOK key

You bring your own Monte Carlo Monte Carlo API token (https://getmontecarlo.com/settings/api). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.getmontecarlo.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Notices

Read-only GraphQL queries. Monte Carlo access is governed by the permissions of the API key's user or service account.

Data sources

• https://apidocs.getmontecarlo.com/ (the API this connector calls, with a BYOK key)

Live from the Monte Carlo API (api.getmontecarlo.com) with a BYOK key; documentation: https://apidocs.getmontecarlo.com/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Monte Carlo. Monte Carlo and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Monte Carlo account.

Built for: Worldwide. Languages: English.

Monte Carlo (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Monte Carlo (BYOK) is. Monte Carlo (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Monte Carlo data: Read your Monte Carlo data observability tables, alerts, monitors, domains, data products and roles with your own API key ID and token (GraphQL queries only). You bring your own Monte Carlo Monte Carlo API token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Monte Carlo call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.getmontecarlo.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Monte Carlo rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Monte Carlo receives. The request we make on your behalf, including the key and the arguments, under Monte Carlo's own terms and privacy policy. Monte Carlo acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Monte Carlo gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Monte Carlo data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Monte Carlo (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Monte Carlo at any time to end all access.

Children. Monte Carlo (BYOK) is a general-audience service operated by the adult using the assistant, under Monte Carlo's own age rules.

Changes. We will post changes here with a new effective date.

Monte Carlo (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Monte Carlo (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Monte Carlo (BYOK) provides: Read your Monte Carlo data observability tables, alerts, monitors, domains, data products and roles with your own API key ID and token (GraphQL queries only). It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Monte Carlo credentials and only access data you are allowed to access. Monte Carlo's terms apply to your use of Monte Carlo; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Monte Carlo. Monte Carlo and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Monte Carlo returns, lightly trimmed; it may be incomplete, delayed or changed by Monte Carlo. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Monte Carlo account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Monte Carlo's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Monte Carlo may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Monte Carlo key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Monte Carlo takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-monte-carlo

Monte Carlo (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-monte-carlo.connectorbay.com/mcp
• REST API: https://byok-monte-carlo.connectorbay.com/openapi.json
• Live status: https://byok-monte-carlo.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Monte Carlo (BYOK) never asks for them.