---
url: /mcp.md
---
# MCP Server

Quarzo Life exposes an [MCP](https://modelcontextprotocol.io) — Model
Context Protocol — server. It lets MCP-compatible clients, such as Claude or
other authorized AI assistants, access and reason about insurance data using
natural language, without writing code against the [REST API](/api/).

The MCP server is designed to make contract information easier to explore,
explain, and integrate into broker and subscriber workflows.

::: warning Work in progress
This page describes the **target scope** of the MCP server. The current
implementation may not yet provide all the capabilities listed here — don't
rely on this page as the exact list of tools available today. Contact the
Quarzo Life team to confirm a specific capability.
:::

## What you can do

Through the MCP server, an authorized client can retrieve information about
contracts, investments, operations, documents, and available funds:

| Category | Covers |
| --- | --- |
| Contract overview | Core details, valuation, performance, fees, available actions. |
| Positions and allocation | Current and historical positions, allocation breakdown, cash balance. |
| Compartments and objectives | Per-compartment allocation, objective progress, transfers between compartments. |
| Operations and transaction history | Past and pending operations, execution timelines, scheduled payments. |
| Fund catalog | Search, details, documents, eligibility, and comparison of funds. |
| Documents and compliance | Contract documents, missing requirements, signature status, consent history. |
| Payments and banking information | Payment instructions, payment/withdrawal status, failure reasons. |
| Alerts and explanations | Contract alerts and plain-language explanations of positions, performance, and operation status. |

See [Capabilities](/mcp/capabilities) for the full, tool-by-tool breakdown,
and [Use cases](/mcp/use-cases) for how brokers and subscribers typically use
this.

## Read-only scope

The MCP server is primarily a **read-only interface**. It retrieves,
summarizes, compares, and explains existing information — it is not intended
to directly submit operations that change the allocation, ownership, or
movement of money on a contract.

This separation reduces the risk of an AI assistant initiating a sensitive
financial operation without the required controls and explicit user
confirmation.

## Operations not available through MCP

The following are intentionally **not** available through the MCP server:

* submitting an arbitrage;
* making a new premium payment;
* submitting a partial or full withdrawal;
* transferring assets between compartments;
* changing a beneficiary clause;
* modifying bank details;
* changing the contract's ownership or subscriber information;
* signing contractual documents;
* any other operation that directly changes money movements or contractual
  rights.

These require the stronger security, validation, audit, and confirmation
mechanisms of the [REST API](/api/) or an authorized Quarzo Life frontend.
The MCP server may retrieve information about these operations and their
status, but it cannot submit them.

## Access and authentication

The MCP server has **no open or anonymous access**: every connection
requires the user to authenticate and authorize the client via OAuth, and
the data returned is scoped to what that authenticated user is already
allowed to see (their own contracts for a subscriber, their book of clients
for a broker).

See [Security](/mcp/security) for the full access-control and auditability
model, and [Connect to Quarzo MCP](/guides/connect-to-quarzo-mcp) to connect a client.

**Next steps:** [Capabilities →](/mcp/capabilities) · [Use cases →](/mcp/use-cases) · [Connect to Quarzo MCP →](/guides/connect-to-quarzo-mcp)