4,500+ servers built on MCP Fusion
Vinkius

Hyrule Compendium MCP. Query creature lore and item stats instantly

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Hyrule Compendium MCP on Cursor AI Code Editor MCP Client Hyrule Compendium MCP on Claude Desktop App MCP Integration Hyrule Compendium MCP on OpenAI Agents SDK MCP Compatible Hyrule Compendium MCP on Visual Studio Code MCP Extension Client Hyrule Compendium MCP on GitHub Copilot AI Agent MCP Integration Hyrule Compendium MCP on Google Gemini AI MCP Integration Hyrule Compendium MCP on Lovable AI Development MCP Client Hyrule Compendium MCP on Mistral AI Agents MCP Compatible Hyrule Compendium MCP on Amazon AWS Bedrock MCP Support

Just plug in your AI agents and start using Vinkius.

Hyrule Compendium: Access detailed data on creatures, monsters, materials, and equipment from Zelda: Breath of the Wild and Tears of the Kingdom.

Use your AI agent to search the entire Hylian ecosystem database by name, ID, or category. Need to know what a Bokoblin drops or where to find a specific material? Your agent handles the lookup instantly.

What your AI agents can do

Get all entries

Retrieves every single entry stored in the Hyrule Compendium database.

Get category

Filters the compendium to get all entries that belong to a specific group, like 'Monsters' or 'Materials'.

Get entry

Fetches complete details for one specific entry using its name or unique ID.

Look up specific game items or creatures

You tell your agent the name or ID of an item, and it returns all associated metadata, including drop locations and properties.

Browse all available game data

The agent pulls every entry from the compendium using get_all_entries, allowing you to see the full range of data available for creatures and materials.

Filter results by game type

You specify a category (like 'Monsters' or 'Materials'), and the agent uses get_category to return only entries belonging to that group.

Understand game ecology and stats

The data provides descriptions and properties, helping you understand how an item or creature functions within the game world.

Supported MCP Clients

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients
Free for Subscribers

Waiting for input…

AI Agent

Hyrule Compendium MCP Server: 3 Tools for Game Data

These tools let your AI agent query the full database. You can retrieve all entries, filter by category, or grab details on a single entry.

get019e5d24

get all entries

Retrieves every single entry stored in the Hyrule Compendium database.

get019e5d24

get category

Filters the compendium to get all entries that belong to a specific group, like 'Monsters' or 'Materials'.

get019e5d24

get entry

Fetches complete details for one specific entry using its name or unique ID.

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
Start building

Make Your AI Do More

Start with Hyrule Compendium, 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

Yo, you gotta connect your AI agent to the Hyrule Compendium. It's your direct line into the entire database for Zelda: Breath of the Wild and Tears of the Kingdom. You can use your agent to dig into everything—creatures, monsters, materials, gear. Need to know what a Bokoblin drops, or where you can score some specific material? Your agent handles that lookup instantly.

get_entry lets you pull all the details on any single item or creature. You just give it the name or the unique ID, and it spits out all the metadata, including where you find it and its properties. You can also use your agent to get the full breakdown on anything you're curious about.

get_category lets you narrow the search. You tell it a category—say, 'Monsters' or 'Materials'—and the agent only gives you entries from that group. This cuts through the noise so you find exactly what you're looking for, whether it's equipment or a specific type of foe.

get_all_entries pulls every single entry in the whole Hyrule Compendium database. If you wanna see the full scope of the Hylian ecosystem, you use this tool. It lets you browse every single data point available for creatures and materials. The data you get helps you understand how things function in the game world, giving you descriptions and properties for everything from common materials to boss monsters.

How Hyrule Compendium MCP Works

  1. 1 Subscribe to the Hyrule Compendium server. No API keys are needed since this is a public data source.
  2. 2 Tell your AI client (Claude, Cursor, etc.) what you want to know—for example, 'What does a Moblins drop?'
  3. 3 Your agent runs the necessary tool (like get_entry) and sends the structured data back to you in plain text.

The bottom line is that you talk to your agent, and it translates that question into a database query for you.

Who Is Hyrule Compendium MCP For?

Lore enthusiasts, game developers, and dedicated players need this. If you spend time researching game mechanics, item locations, or creature stats, this is for you. It takes the guesswork out of massive, complex datasets.

Gaming Content Creator

Needs to quickly pull accurate stats and item drops for guides or wikis without leaving their main workflow.

Lore Researcher

Uses the compendium to build an interactive encyclopedia, cross-referencing details on creatures and historical materials.

Game Developer (Prototyping)

Tests MCP tool-calling capabilities against a clean, structured, and fun dataset for development purposes.

What Changes When You Connect

  • Instantly check drops and locations: Use get_entry to find out exactly what a specific monster or material drops, saving you manual database lookups.
  • View the full scope of the world: Running get_all_entries lets you see every data point in the compendium, giving you a complete picture of the Hylian ecosystem.
  • Target your search instantly: Use get_category to narrow down results. If you only care about 'Equipment,' you don't waste time sifting through monster entries.
  • Build structured guides: The detailed metadata you get back for every entry helps you structure high-quality, accurate guides or wikis.
  • Zero setup time: Since it's a public data source, there are no complex API keys or authentication steps to worry about.

Real-World Use Cases

01

A player needs to know the exact drop rate of a specific monster part.

Instead of opening a dozen wikis, the player asks their agent: 'What does a Bokoblin drop?' The agent immediately runs get_entry on the Bokoblin's ID and returns the full loot table and metadata.

02

A lore researcher wants to map all types of crafting materials.

The researcher asks the agent to list all materials. The agent uses get_category with the 'Materials' filter. This returns a list of potential items (like 'Silent Princess' or 'Voltfin Trout') that can then be individually checked using get_entry.

03

A developer needs a quick data dump of all possible entries.

The developer runs get_all_entries to pull the entire dataset. This allows them to test their MCP tool-calling logic against a massive, clean, and structured dataset without needing to build a local database.

04

A guide writer needs to check equipment details.

The writer asks: 'Show me all types of bow equipment.' The agent uses get_category for 'Equipment' and then uses get_entry repeatedly to pull details on specific bow types, ensuring all stats are correct.

The Tradeoffs

Asking the agent for 'everything'

Prompting the agent with a vague query like 'Tell me about Hyrule' and hoping it magically knows what you want.

Don't be vague. Use get_category first to narrow your focus (e.g., 'Monsters'). Then, use get_entry with a specific name (e.g., 'Moblins') to get the exact details you need.

Trying to filter results client-side

Running get_all_entries and then having your agent try to filter through thousands of entries in the chat window to find the 'Materials' section.

Always use get_category before you start. This limits the data payload and keeps your chat clean. It's much faster.

Assuming a tool can do multiple jobs

Asking get_entry to list all categories, or asking get_all_entries to only show materials.

Use the specific tools for the job. To list categories, you need to prompt for the category list. If you need a single entry, use get_entry. If you need the full list, use get_all_entries.

When It Fits, When It Doesn't

Use this server if your job is based on looking up discrete, verifiable facts about fictional entities. You need to know: What does X drop? Where is Y located? What are the stats for Z? It's perfect for content creation, gaming guides, and knowledge prototyping.

Don't use this if you need complex calculations, relational joins across multiple databases (e.g., 'Show me all monsters that live near rivers AND drop copper'), or real-time data feeds. For those needs, you'll need a specialized data warehouse or a custom integration that handles complex SQL queries. This tool is a lookup service, not a data analytics platform.

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

How we secure it →

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 3 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

get_all_entries get_category get_entry

Manually compiling lore from multiple wikis is a nightmare.

Right now, if you're building a guide, you open a dozen different browser tabs. You check the monster wiki for drops, the material wiki for uses, and the equipment wiki for stats. You copy-paste names, cross-reference IDs, and hope you don't miss anything. It's slow, and you'll spend more time managing tabs than writing content.

With the Hyrule Compendium, you just talk to your agent. You ask, 'What are the drops from a Bokoblin?' and it runs the right tool (`get_entry`) and spits out the clean, structured data you need. You don't touch a single tab.

Use the Hyrule Compendium MCP Server to get data with `get_category`.

Instead of browsing a massive index and trying to remember which section holds the 'Materials,' you tell your agent you need to filter by 'Materials.' The agent uses `get_category` to instantly narrow the focus, keeping your search tight and relevant.

Now you don't just scroll through thousands of names. You pinpoint the exact group you need, making the whole process of compiling structured data fast and reliable.

Common Questions About Hyrule Compendium MCP

How do I find a specific creature's stats using the get_entry tool? +

Use get_entry and provide the creature's name or ID. This tool returns all metadata, including common locations and dropped items, in one go. It’s the most direct way to get deep details.

What if I want to see every single thing in the compendium? +

Run get_all_entries. This tool dumps every entry in the database. It’s useful for seeing the full scope, but remember to use get_category after to filter it down.

Does the get_category tool only work for monsters? +

No. get_category handles all major groups: materials, equipment, monsters, and creatures. Just tell your agent which group you're looking for.

Can I use the Hyrule Compendium MCP Server with my coding IDE? +

Yes. It's designed to work with any MCP-compatible client, including Cursor and VS Code Copilot, letting you pull lore straight into your code or notes.

How do I use the get_category tool to find all types of materials? +

The get_category tool filters entries by type. You just need to specify 'materials' or 'resources' as the category name. This lets you narrow the search to cooking ingredients, crafting components, or upgrade parts.

Does `get_entry` require a specific ID, or can I use a name? +

It accepts both an ID and a name. You can simply pass the common name of the creature or item to the get_entry tool, and it pulls the full metadata for you. This makes lookups much faster than tracking down an ID number.

If I run `get_all_entries`, what happens if the data is too big? +

The get_all_entries tool handles large datasets by paginating results. Your agent will receive data in manageable chunks, preventing timeouts and allowing you to process the entire compendium without issues.

What data fields are available when I use the `get_entry` tool? +

The get_entry tool provides detailed metadata, common locations, and dropped items for any given entry. You get a comprehensive look at the entry's properties and its role in the game world.

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.

You might also like

Built & Managed by Vinkius 30s setup 3 tools

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.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

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.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.