Use Quantra from Claude

Quantra has an MCP server at mcp.quantra.io. Add it to Claude as a connector and Claude can build curves, price swaps, bonds, swaptions, CDS, options and inflation products on the Quantra engine, and show you how each number was computed. Every number comes from the engine. The server computes nothing itself.

Add the connector in claude.ai

1

Settings, Connectors, Add custom connector

Name it Quantra. URL:

url
https://mcp.quantra.io/mcp

There is no sign in. Click Add and it connects.

2

Turn it on in a chat

Open a new chat, open the tools menu next to the attachment button, and enable Quantra. Claude fetches the tool list when the chat starts, so a new chat always has the current tools.

Set up a project

A project gives every chat the same instructions. This is where you tell Claude how to behave with market data, and it matters more than anything the server says. Create a project, open its instructions, and paste this:

project instructions
You are a pricing assistant for business users, backed by the Quantra pricing engine
through the Quantra connector.

Rules that override everything else:
1. You never invent, estimate, recall or type market data of any kind: no curve quotes,
   discount factors, zero rates, volatilities or fixings. Not as placeholders, not as a
   test, not labelled approximate.
2. When the user shows a trade (screenshot, ticket, description) and has not given market
   data, you answer only with: whether it can be priced, exactly which market data is
   missing and in what simple form to paste it (for example "the discount factors from the
   curve screen as date, value rows"), and the conventions you will assume. Then you stop.
   You do not call any pricing or curve tool.
3. Market data exists only once the user has pasted it or attached it in this conversation.
   Then you build the curve from it, price, and put the result next to the number on the
   user's screen.
4. Every number you report comes from the engine. When asked how something is computed or
   why it differs from another system, use the engine's methodology pages and test each
   hypothesis by repricing with one change, rather than asserting a cause.
5. Speak in trade and market terms. Do not mention tools, presets, sessions or request
   bodies unless asked how it works.

Enable the Quantra connector in the project's chats and work inside the project.

What a session looks like

Paste a screenshot of a trade, for example a swap pricing screen from another system, and ask whether Quantra can price it and what it needs. Claude reads the trade off the screen, says which market data is missing and how to paste it, lists the conventions it will assume, and stops. Paste the curve screen. Claude builds the curve from it, checks its discount factors against yours, prices the trade, and puts its number next to the one on your screen.

Then ask the questions that matter:

The answers cite the engine source at the pinned version, file and line, with a link to the line on GitHub. The engine is open source, so you can check every claim.

Rules the server enforces

Other clients

Claude Desktop uses the same custom connector setting as claude.ai. Claude Code:

terminal
claude mcp add --transport http quantra https://mcp.quantra.io/mcp

Cursor and other MCP clients: add a server of type streamable HTTP with the same URL.

Running it yourself

The server is a small Python package that talks to any Quantra engine over its JSON API. Run the engine and point the server at it with QUANTRA_ENGINE_URL. The repository has the install steps, a Dockerfile and a compose file with both services: github.com/joseprupi/quantra-mcp. It needs engine 0.7.0 or later.

Public demo mcp.quantra.io runs on the same machine as the demo and prices on engine 0.7.0. It has no authentication and is rate limited per client. It is for trying things out, not for production use.