Yu-Gi-Oh MCP. Get stats for any card, no wiki needed.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Yu-Gi-Oh MCP Server gives your AI agent instant access to a full card database. Search for any card's detailed stats, list all current archetypes, or check entire set contents using specific tools like `get_card_info` and `list_archetypes`.
Stop manually checking wikis; just talk to the data.
What your AI agents can do
Check db version
Checks the current version number and last update timestamp of the entire card database.
Get card info
Retrieves detailed stats, descriptions, and images for one or multiple specific cards.
Get card set info
Fetches comprehensive details about a single, specified card set.
Your agent fetches stats, descriptions, and images for one or more cards using get_card_info.
The server lists every recognized Yu-Gi-Oh! card archetype using the list_archetypes tool.
Your agent retrieves a list of all major and minor card sets published by Konami via list_card_sets.
The server pulls the full contents and context for one selected card set using get_card_set_info.
Running get_random_card instantly delivers data for a single, randomly drawn card from the entire database.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Yu-Gi-Oh: 6 Tools for Card Database Lookups
Use these six specific tools to query, list, and retrieve structured data from the comprehensive Yu-Gi-Oh! card database.
019e5d68check db version
Checks the current version number and last update timestamp of the entire card database.
019e5d68get card info
Retrieves detailed stats, descriptions, and images for one or multiple specific cards.
019e5d68get card set info
Fetches comprehensive details about a single, specified card set.
019e5d68get random card
Pulls the data for one random Yu-Gi-Oh! card from the entire database.
019e5d68list archetypes
Lists all major and minor archetypes recognized within the game's history.
019e5d68list card sets
Provides a complete list of every published card set available in the database.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Yu-Gi-Oh, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Yu-Gi-Oh MCP Server - Card Data Queries
Your AI client gets instant, structured access to the entire Yu-Gi-Oh! card database. You never gotta manually check a wiki again; you just talk directly to the data and let your agent pull exactly what you need.
When you connect your agent, it can use several specific tools. These functions handle everything from checking basic stats for one monster to listing every single set Konami ever published. You'll find that your AI client knows how to query structured card information across multiple domains—be it searching for a specific Level 4 spell or tracking down the exact ATK/DEF values of an obscure boss monster.
Card Data Retrieval and Inspection
To pull stats, descriptions, and images for one or more specific cards, your agent uses the get_card_info tool. This function fetches detailed data points like Level, Type, Attribute, ATK value, DEF value, and the full card text description for whatever criteria you give it, supporting searches even if you aren't totally sure of the exact name.
For a deeper dive into specific cards, the get_card_set_info tool lets your agent pull comprehensive details about a single, specified card set. This isn't just listing names; it provides the full context and contents for that entire expansion or collection you're interested in studying.
Need a quick reference point? Running get_random_card instantly delivers all the raw data—stats, description, image metadata—for one completely random card pulled straight from the database. This is perfect if you're just looking for some inspiration and don't know what to search for.
Database Scope and Exploration
Your agent can scope out the entire universe of cards by checking the data source itself. The check_db_version tool reports the current version number and the last update timestamp for the whole card database, so you always know if your information is up to date.
To see what themes are out there, the server uses list_archetypes, which pulls a list of every recognized major and minor archetype in Yu-Gi-Oh! history. This lets your agent quickly identify all known deck themes for synergy planning or brainstorming purposes.
If you wanna know what card sets exist generally, your agent runs list_card_sets to get a complete listing of every published set available in the database. You can then use this list to select a specific set and run get_card_set_info. The combination of these tools lets you browse through Konami's entire publishing history and drill down into any single collection without ever getting lost.
Basically, your agent handles all the complex data structure querying for you. It pulls everything from basic stats to deep set contents using structured calls like get_card_info or list_archetypes, letting you focus on building decks instead of cross-referencing wikis.
How Yu-Gi-Oh MCP Works
- 1 First, subscribe to this server and enter your API credentials into your AI client.
- 2 Next, prompt your agent with a request (e.g., 'What are the stats for Blue-Eyes White Dragon?').
- 3 Your agent recognizes the need for card data and calls
get_card_info. It returns structured JSON containing the monster's details.
The bottom line is, your AI client acts as the middleman, running specific database lookups so you get clean data instead of messy text.
Who Is Yu-Gi-Oh MCP For?
This is for anyone who needs card game data structured and available via an API call. If you're a developer building a companion app, or a content writer constantly verifying rules, this saves hours of manual research. It’s built for people whose job involves consuming massive amounts of niche technical data.
Uses list_archetypes and get_card_info to quickly check card effects, determine synergy between monsters, or balance new rulesets.
Integrates the server into a larger system by calling multiple tools (list_card_sets, then get_card_set_info) to map out data relationships for a project.
Needs quick, verifiable stats and descriptions. They use get_card_info or get_random_card to populate articles or write lore without leaving their chat window.
What Changes When You Connect
- Instantly verify data accuracy. Use
check_db_versionto confirm the database is running on the latest TCG/OCG standards before you start building anything. - Stop guessing about themes. Run
list_archetypesto pull every single official deck theme in one go, perfect for brainstorming new game content. - Speed up your research workflow. Instead of navigating multiple wiki pages, a single prompt triggers
get_card_info, giving you the monster's Level, ATK, and DEF immediately. - Map out entire collections. Use
list_card_setsto see every set released, then callget_card_set_infoto pull all contained cards for an inventory audit. - Never get bored writing lore again. Run
get_random_cardand instantly get a card's full data packet—a quick write-in or challenge prompt.
Real-World Use Cases
Checking a key duelist card's stats
A content writer needs to verify the exact ATK and DEF of 'Blue-Eyes White Dragon'. They use get_card_info directly, getting structured data that proves the monster's Level 8 status without any guesswork.
Brainstorming new deck synergies
A game designer wants to see what kind of themes exist. They use list_archetypes. The resulting list provides immediate categories they can build a balanced, theoretical card around.
Auditing an entire collection's source material
A collector needs to know which sets were released in 2015. They run list_card_sets, narrow down the list, and then use get_card_set_info on that specific set ID for a full contents dump.
Building an automated random challenge generator
A developer builds a game feature that needs daily novelty. They call get_random_card, which provides all necessary stats and lore for the card, allowing the application to run without needing manual data input.
The Tradeoffs
Searching by vague concept
Asking the agent: 'Tell me about powerful dragons.' This is too vague. The server doesn't know if you mean ATK or lore, and it can't run a general search.
→
You must use get_card_info with specific parameters (e.g., card name) or first filter the list using list_archetypes to narrow down the scope.
Assuming one call covers everything
Calling only get_card_info('Card X') and assuming you get the set context. You might miss critical meta-data about which specific expansion it belongs to.
→
Always pair card lookups with list_card_sets first, then use get_card_set_info to ensure you have complete contextual metadata.
Forgetting the database status
Running a complex query and getting questionable results. You don't know if the data is from 2018 or today.
→
Start by calling check_db_version. This confirms whether your agent is reading the absolute latest TCG/OCG records, preventing outdated information.
When It Fits, When It Doesn't
Use this server if your task requires querying verifiable card game data. Specifically, use it when you need to look up stats (get_card_info), identify themes (list_archetypes), or map out sets (list_card_sets).
Don't use this if your goal is general discussion about the game—your agent can talk that stuff without tools. Also, don't assume a single tool does it all; if you need both set context AND card details, you must run list_card_sets first, followed by get_card_set_info, and finally use get_card_info. If the data is only for fun or highly theoretical, stick to general chat. This tool requires specific, verifiable inputs.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Yu-Gi-Oh. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 6 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Diving into card game research shouldn't feel like navigating a thousand wikis.
Before this server, finding the stats on a specific monster meant clicking through multiple linked pages: checking the wiki for the name, then searching Konami archives to find the set ID, and finally cross-referencing external sites just to verify its ATK/DEF values. It was slow, manual, and prone to copy-paste errors.
Now, your agent handles it all in one go. You ask: 'What are the stats for Blue-Eyes White Dragon?' The agent runs `get_card_info`, pulls the Level 8 data instantly, and returns a clean JSON object. No more tabs, no more ambiguity.
Yu-Gi-Oh MCP Server: Structured card data in your workflow
The manual process of listing available sets meant running separate searches for 'Set A,' 'Set B,' and 'Set C' to see what cards were released. You’d never get the full picture without manually combining dozens of results.
With this server, calling `list_card_sets` gives you a complete list of every set ID. Then, running `get_card_set_info` on that ID delivers all card data in one structured block—it's immediate and exhaustive.
Common Questions About Yu-Gi-Oh MCP
How do I use get_card_info to search for a card? +
You pass the card name or its unique ID as an argument. For example, 'get_card_info(name='Dark Magician')'. It returns all core stats like ATK and DEF.
What is the difference between list_archetypes and get_card_info? +
list_archetypes gives you a master list of themes (like 'Dragon' or 'Spellcaster'). get_card_info gets the specific stats for one card within an archetype.
Can I use get_random_card to build a game feature? +
Yes. Calling get_random_card delivers immediate data—stats, type, and description—for a usable card without any setup or guessing required.
Does check_db_version tell me if the cards are legal for modern play? +
It confirms the database version and last update timestamp. You'll need to use get_card_info and reference external rulings for current legality, but it verifies data freshness.
How do I get all possible card sets available? +
Run list_card_sets. This returns a clean array of every set name or ID in the database. You then use these IDs for further queries like get_card_set_info.
When I use `get_card_set_info`, what data structure can I expect for a set? +
The output provides structured JSON detailing the entire card pool for that set. You get metadata like the total number of cards and the release date, making it easy to programmatically iterate over all included card IDs.
If I run `get_card_info` with a large list of names, is there rate limiting? +
Yes, there are usage limits. If your agent hits the cap, it will return an HTTP 429 error code. You'll need to build a backoff strategy into your client code to retry requests.
How do I use `get_card_info` to search by stats (ATK/DEF) instead of just name? +
You pass specific parameters like ATK, DEF, and Level directly in the query body. This lets your agent filter results quickly without having to pull every card record first.
How can I find the specific effects and stats of a card by its name? +
Use the get_card_info tool with the name or fname parameter. The agent will return full metadata including ATK/DEF, Level, Type, and the official card text.
Is there a way to see all the different card themes or archetypes available in the game? +
Yes! Run the list_archetypes action. It will provide a comprehensive list of all archetypes currently recognized in the database, such as 'Elemental HERO' or 'Blue-Eyes'.
How do I know if the card data is up to date with the latest releases? +
You can use the check_db_version tool. It returns the current database version and the timestamp of the last update from the YGOPRODeck servers.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
UUID Generator API
Generate unique identifiers — audit UUIDs and versions via AI.
Tencent CloudBase / 腾讯云开发 TCB
China's dominant serverless platform — orchestrate cloud functions, databases, and storage via AI.
Object Hash Engine
Generate deterministic SHA-256 fingerprints of any JSON object. Keys are automatically sorted so {b:2,a:1} and {a:1,b:2} always produce the exact same hash. Essential for deduplication.
You might also like
PredictHQ Event Intelligence
Manage global events — audit festivals, sports, and rankings via AI.
TextP2P
Send peer-to-peer text messages at scale for political campaigns, nonprofits, and organizations that need personal outreach.
SonarCloud
Merge your SaaS DevOps workflow with SonarCloud to review AI code and prevent production vulnerabilities.