What syncs
- Your holdings, balances and allocation, read on request rather than copied anywhere.
- Net worth history and the accounts behind it.
- Budget and cash-flow figures you have entered.
- Projection and backtest results Killion has already computed for you.
What the connection cannot do
These are not policy commitments. The access scope Killion requests does not include them, so no bug, breach or change of heart could turn them on.
- Place a trade or move money. It inherits the same read-only posture as every other connection.
- Change anything in your Killion account. The connector exposes reads only.
- See anything while you are signed out. Access is bound to an OAuth token you grant and can revoke.
- Act on its own. It answers when you ask, inside a chat you started.
Practical notes
Authorisation runs over OAuth 2.1. You approve the connection from Claude and can revoke it from either side; Killion never sees your Claude account credentials.
Your own Claude subscription pays for the model, so using the connector consumes none of the AI budget included with your Killion plan.
It requires an active Killion subscription, because it reads the same data the paid product computes.
MCP is an open protocol, so the same server works with any MCP-capable client, not only Claude.
How to connect
In Claude, open Settings, then Connectors, then Add custom connector, and give it the Killion connector URL. Claude sends you to Killion to authorise the connection, and you approve it with the account you already use. From then on you can ask about your own holdings, allocation or projections in an ordinary conversation.
Not available yet. The server is built but has not been released, so the connector cannot be added in Claude today. This page describes what it will do rather than something you can switch on right now.
Other integrations
- SnapTrade — The read-only linking layer behind every brokerage and crypto connection in Killion.