Tools & limits
The 83 MCP tools by area, and how plan limits apply through MCP.
The server exposes 83 tools — 33 read, 50 write:
| Area | What the tools cover |
|---|---|
| Collection insights | Search what you own, collection summary & value, portfolio history, find a card everywhere it lives, available copies |
| Catalog & prices | Full catalog search, card details, per-card price history with trends, and one or many cards priced in every store at once, with what Card Kingdom and Star City Games pay |
| Decks | List/read/value decks, missing cards; create, edit, delete, set commander, folders, add/remove cards in bulk, set card quantities; put cards in categories, tag and untag them, and ask Silvane to suggest categories; mark cards (or the commander) as a proxy or as untracked, and say that several tracked decks share one copy of a card |
| Binders & lists | List/read collections; create, rename, delete, folders, add/remove cards in bulk, set cards |
| Watchlist | Read the watchlist; add/remove cards, manage folders |
| Sales | Read and summarise the sell side of your Ledger; record sales, fix prices, dates and notes, add or remove cards, group sales into batches, share a sale as a receipt link |
| Purchases | Read and summarise the buy side; record purchases with vendors, shipping, fees and discounts, fix lines, mark orders paid or received |
| Ledger | The unified money read: in, out and net with monthly trend, and top sets by money moved |
| Price alerts | Read alerts; create and delete them |
| Views, trading & account | Run saved views, For Trade & Wants lists, connection check |
The full interactive reference lives at silvane.app/mcp.
Prices through MCP
Every tool that returns an amount answers in your active price source — and declares which source and currency the numbers are in, so your assistant can say "that's the Cardmarket trend price, in euros" instead of guessing. Two of the exceptions show up here:
- The Ledger answers from its own recorded prices — a sale or purchase line is the record of the deal, not a market quote, so those numbers never move with your source.
- Views with a pinned price filter filter in the view's source, so the assistant sees the same card list you and every other viewer do.
One tool answers in every source at once: comparing prices. Ask "where is this cheapest" or "what would Card Kingdom pay for these" and the assistant gets each card's price in all five sources — TCGplayer, Cardmarket (in euros), Card Kingdom, Mana Pool and Star City Games — plus the Card Kingdom and Star City Games buylists, for up to 100 cards at a time. A store with no price for a card is left out rather than shown as zero.
Adding cards in bulk
Cards go in and out a list at a time, not one at a time — a whole decklist or a whole haul is a single call, so an assistant can finish it in one turn instead of stalling halfway through a hundred cards.
Because most playable cards have dozens of printings, the printing is chosen for you rather than asked about. You can say which rule to use:
- The one you already own — the default for decks, so a tracked deck reserves the copy actually in your binder.
- The cheapest — the default for binders and lists, since recording a purchase usually means the cheap printing.
- The newest — the most recent reprint.
Just say which you want ("use the cheapest printings") and the assistant
passes it through. To pin an exact printing, give its set and collector
number the way a decklist writes it — 1 Sol Ring (LTC) 284 adds that
Sol Ring and no other; if that set and number don't exist, the card is
reported back instead of swapped for another printing. Names it cannot match are reported back individually
and never stop the rest of the list.
The Ledger through MCP
You can keep both sides of your Ledger from the
conversation. On the sell side: record who bought what and for how much,
correct a price after the fact, mark a sale paid or delivered, and group
an afternoon's sales into a batch. On the buy side: record purchases with
their vendor, shipping, fees and discounts, and walk each order through
ordered, paid and received. And across both, ledger_summary and
ledger_top_sets answer the money question the app's Overview answers —
what came in, what went out, and where it moved.
Every summary follows the hub's rule: only orders marked paid count as money — what you're owed, and what you've committed but not paid, are reported apart, never folded into revenue or spend.
You can also hand a buyer their receipt link from the conversation. Publishing is always an explicit step: asking for a sale's link mints it and leaves it off, so nothing becomes readable until you say to turn it on — and the same call switches it back off.
Selling does not empty your binder — and buying does not fill it
Recording a sale here never removes cards from your collection, and recording a purchase never adds them. Unloading sold cards and loading a purchase into binders are deliberate steps you do in the app — they are the hardest things in the feature to undo, so they are not something an assistant can do on your behalf. Purchase lines already loaded are frozen except for their price.
Sales and purchases, unlike cards and decks, are deleted permanently: deleting one is permanent.
How much one call may carry
A tool call is capped so a single request cannot run away:
| Call | Cap |
|---|---|
| Cards in one bulk add, edit or move | 500 |
| Decks in one share | 10 |
| Tags in one call | 20 |
Larger jobs are split across calls, and the assistant does that on its own.
Quotas and Pro through MCP
MCP follows the same rules as the app:
- Free quotas apply — if your free account has 3 binders, a
create_collectioncall for a 4th is rejected with a clear message, exactly like in the app. - Pro gates apply — Pro-only data (for example price-history ranges beyond 90 days) stays Pro through MCP.
- The Ledger is Pro — every sales, purchases and ledger tool requires Silvane Pro, exactly as the Ledger hub is in the app.
- Reading your collection is always free — loading your cards into Claude or ChatGPT is never paywalled.
Privacy note
Data an authorized client reads flows to that AI provider under their privacy policy. You choose the client, you control the prompts, you can revoke access at any time. See our Privacy Policy.