CLAUDE, CONNECTED
Let an assistant act as you, at an authority you choose.
How to connect Claude, ChatGPT, Hermes Agent or another MCP client to Meridian, what the four rungs mean, what a connection can never do, and how to end one.
THE SHAPE
A connection reaches in; it does not hand anything out
Connecting an assistant lets an MCP client - Claude, ChatGPT, Hermes Agent or another - call Meridian tools as you. It does not hand over your exchange credentials - those stay sealed in the worker vault and are readable by nothing else - and it never raises what your plan allows.
The connection is created from the assistant side. You add the Meridian server to a client, the client sends you back to Meridian to agree to an authority, and the connection appears in Settings once you do.
CONNECT
Four steps, once
Copy the server URL
Settings, then Connections, shows this deployment server address and the setup for each client, with every line ready to copy.
Open SettingsAdd it to your client
Each client takes the server in its own place: Claude under Connectors, Claude Code with claude mcp add, ChatGPT as a plugin in Developer mode, Hermes Agent in config.yaml with auth: oauth. Choose OAuth wherever a client asks - there is no API key. The address must match byte for byte, including the path - a near miss fails later with no visible cause.
Agree to a rung
The client sends you to Meridian to consent. Pick the lowest authority that lets the assistant do what you actually want it to do.
Check it in Settings
The connection is listed with the rung you chose, when it was made and when it was last used.
THE LADDER
What each rung permits
A rung bounds the connection. It never raises the account: an operate rung on a plan without live trading still cannot trade.
| Rung | What it can do | Plan |
|---|---|---|
| observe | Read what your account can already read. | Every plan |
| author | Create and change documents - strategies, plans, notes. | Pro |
| operate:paper | Start and stop paper execution. | Pro and above, within your slots |
| operate:live | Act on live execution, within the same limits you have. | Quant |
BOUNDS
What a connection can never do
It cannot exceed your plan. A rung narrows what a connection may do; it never widens what the account may do, so nothing reachable through an assistant is unreachable in the browser.
Live actions carry a daily cap of their own, counted per account, and a confirmation that can only be spent once. An assistant that asks twice acts once.
- Revoking is immediate on the next callEnding a connection in Settings stops it the next time it tries to act. There is no window in which a revoked grant still works.
- Every action is auditedThe connection row carries what was done through it, so what did the assistant change is a question with an answer.