MTG collection for Cursor / Claude Code: your cards beside your code

Q: Is there a REST API too?

Yes. Every tool is also a REST call under /api/v1, signed in with the same OAuth: see the deck API page.

Updated November 9, 2026

Your MTG collection works in Cursor and Claude Code the same way it works in a chat assistant: Reliquary is a remote MCP server at https://reliquary.gg/mcp, both tools can add one and sign in to it with OAuth, and then your cards, decks and places are a question away from your editor or terminal.

What each tool supports

	Cursor	Claude Code
Remote server over HTTP	Streamable HTTP, per Cursor's docs	The HTTP transport, per Anthropic's docs
OAuth sign-in	Supported for servers that require it	Supported

The exact lines for Reliquary are on Connect your assistant.

Why a developer would want it

Lists as files. export_deck gives a deck as plain decklist text and export_collection the whole collection as CSV, in Moxfield's or Deckbox's columns. Keep them in a repository, diff them, script them.
Lists from files. import_deck takes decklist text and makes a deck; import_batch takes collection rows already parsed from a CSV file, 500 rows a call.
The same rules everywhere. Every copy has one place, a deck claims its copies, a copy two decks share is named with both, and a proxy is named as one and left out of a value unless you ask. The rules are the same in an editor as in a chat.
Changes ask first. Each tool declares whether it reads, adds, or changes and removes, and the destructive ones only describe what they would do until confirmed.