Hyrule Compendium MCP for AI. Access all Zelda game data via natural conversation.
Works with every AI agent you already use
…and any MCP-compatible client








How this MCP server connects to your AI agent
The Hyrule Compendium MCP provides instant access to a full database of Zelda: Breath of the Wild and Tears of the Kingdom data.
Use your agent to search creature details, find specific materials for crafting, or list all known monster types from across Hyrule's ecosystem.
What AI agents can do with Hyrule Compendium Automation
Get all entries
Retrieves every single entry in the entire Hyrule Compendium database.
Get category
Filters and retrieves all entries belonging to a specific group, such as materials or monsters.
Get entry
Gets detailed information for one item, monster, or creature using its unique name or ID.
Retrieves every record available in the compendium, allowing you to get a full inventory of everything cataloged.
Narrows down results to specific groups like monsters, materials, or equipment for focused research.
Looks up detailed metadata, common locations, and dropped items using the name or unique ID of an entry.
Ask an AI about this
Waiting for input…
What AI agents can do with Hyrule Compendium: 3 Tools Available
These tools let your agent pull detailed records by retrieving all entries, filtering specific groups, or looking up one item using its name.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Hyrule Compendium on VinkiusGet All Entries
Retrieves every single entry in the entire Hyrule Compendium database.
Get Category
Filters and retrieves all entries belonging to a specific group, such as materials...
Get Entry
Gets detailed information for one item, monster, or creature using its unique name...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
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 Hyrule Compendium, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ 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
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Hyrule Compendium. 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
Built on the Model Context Protocol (MCP) for 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 connection provides 3 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Tracking Game Lore By Hand Is Painful, Solved with Vinkius AI Gateway
Think about trying to compile a guide for Hyrule's flora and fauna. You open one wiki tab, copy down the monster name; switch tabs to check its drop items; then you have to start another search just to find out what kind of material it leaves behind. It’s constant clicking, opening multiple browser windows, and manually cross-referencing data points.
With this MCP, that process vanishes. You ask your agent about the monster parts. It automatically pulls all required details—the full description, its category, and drop items—and gives you a single, clean answer. What you get is immediate, consolidated knowledge.
Using the Hyrule Compendium MCP for Specific Data Access
Instead of searching multiple endpoints, you tell your agent exactly what you need. You can ask it to first run `get_category` to narrow down 'materials', and then use that filtered list to help find a specific item's details using `get_entry`.
The data retrieval process moves from being manual research into automated query execution. It’s about asking the right question to get the perfect, structured answer every time.
What your AI can actually do with this
This MCP connects your AI client directly to an encyclopedia built around the world of Hyrule. You can talk naturally about the game and get precise facts back—whether you need to know a rare material’s source or want a full list of all known enemies. Instead of sifting through wikis, you ask your agent for details on any creature, monster, or piece of equipment by its name or ID.
If you're working with data like this regularly, check out the Vinkius catalog; it hosts thousands of other specialized databases just like this one. It’s built to handle everything from basic lookups—like finding what a 'Big Hearty Truffle' does—to getting every single entry in the database for a complete overview.
019e5d25-1242-708b-86e5-b5558a2409a6 Here's how it actually works
The bottom line is that you talk to your agent like you're talking to a friend, and it handles the database queries for you.
Subscribe to this MCP on Vinkius. No complex API keys are needed since this is a public data source.
Connect your agent (Claude, Cursor, etc.) to the catalog via its compatible client app.
Ask anything about Hyrule's wildlife, weapons, or materials using natural language prompts.
Who is this actually for?
Zelda players who need quick data checks without pausing gameplay. Lore enthusiasts researching the game’s deep-cut details. Developers testing data retrieval patterns with clean, structured datasets.
Needs to cross-reference hundreds of materials or monster types quickly to build a comprehensive wiki or database.
Wakes up needing detailed descriptions and ecology notes for Hyrule's inhabitants, treating the game like an interactive encyclopedia.
Needs a reliable way to test tool-calling logic against predictable, structured data before integrating it into a live build.
What Changes When You Connect
Stop manually searching wikis. Use your agent to ask for specific stats or locations, getting the exact facts instantly.
Need a full overview? Running get_all_entries gives you access to every piece of lore in one go, perfect for compiling massive data sheets.
Focus your search immediately with get_category. You can narrow down results by 'materials' or 'monsters' without sifting through irrelevant entries.
Use get_entry when you know exactly what you need. Just give the name, and it pulls up location, drop items, and full descriptions.
The data is clean and structured. This makes it ideal for developers who need a predictable dataset to test their client-side logic.
See it in action
Checking rare monster drops
A player needs to know if the Lynel parts found in Hyrule Ridge are worth gathering. They ask their agent, and it uses get_entry to confirm drop items and common locations immediately.
Building a materials guide
A researcher wants to compile every type of plant material used in cooking. They ask the agent to filter using get_category, focusing only on 'materials' for an organized list.
Reviewing entire game lore
An enthusiast wants a complete, un-filtered look at all entries—creatures, items, and monsters alike. They ask the agent to run get_all_entries to get the full scope of the world.
Developing data pipelines
A developer needs a stable dataset for testing new features. They use all three tools—first get_category, then refine with get_entry—to validate their retrieval logic across multiple endpoints.
The honest tradeoffs
Asking general questions
Telling your agent, 'Tell me about the game.' The response will be vague and won't give you structured data on drops or stats.
If you want a full list, explicitly ask the agent to use get_all_entries. If you only care about one thing, like materials, specify that first.
Skipping filtering
You are looking for equipment but don't know the category name. You might try listing everything and getting overwhelmed by results.
First, ask the agent to use get_category and specify 'equipment'. This immediately limits your search scope.
Ignoring IDs
You know a monster exists but only remember part of its name. You might fail to find it because you didn't provide enough context.
Try using get_entry with the closest known ID or partial name; the agent handles the lookup process for you.
When It Fits, When It Doesn't
Use this MCP if your core problem is structured data retrieval from a massive, fixed knowledge base. You need to know what things are and where they come from. If you need to list everything available in the database, use get_all_entries. If you want to focus on one specific type of thing—like just monsters or just materials—use get_category. Finally, if you've already narrowed it down and only care about details for a single entry, like 'Blue Sparrow', then run get_entry. Don't use this MCP if your goal is general conversation; treat the agent as an API wrapper that needs precise instructions to do its job right.
Questions you might have
How do I use the get_all_entries tool? +
Just ask your agent to retrieve all entries in the compendium. It will pull a comprehensive list of everything available, from creatures to materials.
What should I use if I only want to see monsters? +
You need to run get_category and specify 'monsters' as the group. This keeps your search focused and prevents getting flooded with unrelated item data.
Can get_entry look up a creature by name? +
Yes, you can use get_entry to find details for any monster or creature if you know its name or unique ID. It provides full metadata and drop lists.
Is this MCP good for developers? +
It’s great for developers because it gives a clean, predictable dataset. You can use the three tools to test your client's ability to handle scoped versus global data retrieval.
When I call get_all_entries, what structure does the returned Hylian lore use? +
It returns structured JSON objects containing metadata for every entry. This includes common locations, specific types, and dropped items, making it easy for your agent to parse into a database or spreadsheet.
If I want to narrow my search using get_category, what are the available filters? +
You can filter by major groups like 'monsters,' 'materials,' and 'equipment.' Using this function keeps your results focused, preventing you from wading through irrelevant data.
What happens if I try to use get_entry with an ID or name that is invalid? +
The tool returns a clear error message stating the entry was not found. This prevents confusion and allows your agent to prompt you for clarification or suggest related entries.
When get_entry fetches a specific item, what key details beyond the description do I receive? +
It provides actionable metadata points, including common locations within Hyrule and items that drop when the creature is defeated. This turns lore into useful game data.
How can I find the stats for a specific creature like a 'Golden Horse'? +
Use the get_entry tool and provide 'golden_horse' as the id_or_name. The agent will return its common locations, drops, and description in seconds.
Can I list only the weapons and armor available in the game? +
Yes. Use the get_category tool with the category_name set to 'equipment' to see all gear recorded in the compendium.
Is it possible to browse the entire compendium at once? +
Absolutely. The get_all_entries tool fetches the complete database, organized by category, allowing your AI to act as a full Hylian encyclopedia.
We've already built the connector for Hyrule Compendium. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 3 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.