Lorcana MCP Server

Lorcana MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Disney Lorcana TCG MCP server with card search, deck analysis, ink curves, and set browsing.

What you get

• search_cards — -- Search cards by name, rules text, ink color, type, rarity, set, or cost range
• browse_sets — -- List all sets or drill into a specific set to see its cards
• character_versions — -- Compare all printings of a character across sets
• browse_franchise — -- Browse cards by Disney franchise (Frozen, Moana, etc.)
• analyze_ink_curve — -- Analyze a deck list for ink cost distribution, inkable ratio, and color balance
• analyze_lore — -- Analyze lore generation in a deck or find top lore-generating cards

What the assistant can call

Once Lorcana is connected, these are the calls the assistant has available:

• search_cards — Search Disney Lorcana cards by name, rules text, or filters (ink color, type, rarity, set, cost range). Returns paginated results
• browse_sets — List all Disney Lorcana sets, or drill into a specific set to see its metadata and cards
• character_versions — Show all printings/versions of a Disney Lorcana character across sets. Useful for comparing different versions of the same character
• browse_franchise — Browse Disney Lorcana cards by franchise (story). Without a franchise name, lists all franchises with card counts. With a franchise name, shows cards
• analyze_ink_curve — Analyze a Disney Lorcana deck list for ink cost distribution, inkable ratio, and color balance. Paste a deck list to get curve analysis
• analyze_lore — Analyze lore generation in a deck list, or find the top lore-generating cards. In deck mode, shows total lore potential and efficiency ranking. In
• find_song_synergies — Find Disney Lorcana song synergies. Given a Song, find characters that can sing it. Given a Character, find songs they can sing. With no input

Setting it up

The server ships on npm as lorcana-oracle, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Lorcana's toolset — search_cards, browse_sets, character_versions and 4 more — is a fair guide to whether it matches your workflow. It is maintained by gregario; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the lorcana mcp server does with a few real requests.