MODEL CONTEXT PROTOCOL
Your Rate Board, Now a Tool Your AI Assistant Can Use
Exchange Rate Management has a built-in MCP server. Connect Claude — or any assistant that speaks MCP — with the API key you already have, and manage your board in plain language: read today's rates, update a price, pause automation. With guardrails designed for the ways AI gets things wrong.
WHAT YOU CAN SAY
Talk to your board the way you'd talk to staff
“What's on my rate board right now, and when did each pair last update?”
“Set USD → CAD to buy 1.3720, sell 1.3980.”
“The market is jumpy today — pause automatic updates on EUR → CAD until I say otherwise.”
“Did automation run this morning? Any pair that needs my attention?”
“Resume automation on USD → CAD; the price on the board now is fine as the baseline.”
The assistant reads live values before it acts, confirms big changes with you, and every update is on your website and shop TV within about half a minute — the same path a dashboard edit takes.
THE TOOLS
Five tools, scoped to your account
get_board
Reads every pair on your board: buy and sell price, visibility, and when each was last updated.
set_rate
Updates the buy and sell price of one existing pair — in two steps. The assistant must first read the current values, then echo them back exactly to commit, so it can never overwrite a price it hasn't seen.
get_automation_status
Reads your automatic-daily-rates setup: which pairs are automated, their margins, their state, and when the market feed last updated.
pause_automation
Turns automatic updates off for one pair. Prices and margin settings stay exactly as they are.
resume_automation
Turns automatic updates back on for a paused pair, accepting the price currently on the board as the new baseline — the same thing the Resume button in the dashboard does.
SETUP
Connect in about a minute
You need two things: the endpoint and your API key — the same erm_key that's already in your widget embed code, copied from the dashboard.
claude.ai (custom connector)
In claude.ai, go to Settings → Connectors → Add custom connector, and paste the endpoint with your key attached:
https://exchangerate.management/api/mcp?key=erm_YOUR_KEYClaude Code
One command in your terminal:
claude mcp add --transport http rate-board \ https://exchangerate.management/api/mcp \ --header "Authorization: Bearer erm_YOUR_KEY"
Any other MCP client
It's a standard remote MCP server: Streamable HTTP at https://exchangerate.management/api/mcp, no sessions, POST only. Most clients take a config like this:
{
"mcpServers": {
"rate-board": {
"type": "http",
"url": "https://exchangerate.management/api/mcp",
"headers": { "Authorization": "Bearer erm_YOUR_KEY" }
}
}
}Prefer the Authorization: Bearer header where your client supports it — it keeps the key out of URLs and logs. X-Api-Key and ?key= also work, for clients that can only take a bare URL.
GUARDRAILS
Built for assistants that occasionally get it wrong
Your board shows real prices to real customers, so the server treats every AI-proposed change the way it treats the market feed: useful, and not blindly trusted.
Two-step confirmation on every write
set_rate never writes on the first call. It reports the current prices, and the assistant must echo them back exactly to commit. If the board changed in between, the write is refused.
Large moves are refused
A change of more than 50% is rejected outright — 13.98 typed for 1.398 is a fat-finger, not a price. Changes over 10% go through, but carry a warning the assistant is told to relay to you first.
No new pairs, no inverted quotes
The assistant can only update pairs you already created — a hallucinated currency code can't become a row on your shop's board. And a sell price below the buy price (a guaranteed loss on every trade) is refused.
Automation notices AI edits, exactly like hand edits
If an assistant writes a rate on an automated pair, automation pauses itself on that pair at the next run — the same protection you get when you edit by hand. Nothing silently overwrites a human (or AI) decision.
Your key, your board, nothing else
The connection is authenticated by your own API key — the same key that already powers your widget. It can only see and change the rates of the account it belongs to.
FAQ
MCP questions, answered
Already a customer? You're one paste away.
Your API key already works here — copy it from the dashboard and add the connector. New here? The Free plan includes the board, the widget, and the MCP server.