Ice And Fire MCP. Query Westeros's lore, characters, and houses instantly.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
An API of Ice And Fire lets you query the entire A Song of Ice and Fire universe directly from your AI agent.
Use it to list books, find character biographies, and map out noble houses of Westeros. Get specific details on titles, lineage, and lore without leaving your workflow.
What your AI agents can do
Get book
Retrieves specific metadata for a single book in the series.
Get character
Retrieves full details and metadata for a specific character.
Get house
Retrieves full details and metadata for a specific noble house.
Use list_books to retrieve a full list of titles, and then use get_book to pull specific metadata for any entry.
Run list_characters to filter thousands of characters by culture, gender, or name. Use get_character to get full profiles, including aliases and family connections.
Use list_houses to browse houses by region or motto. Then, use get_house to retrieve a complete profile for a specific noble family.
Your agent can check the relationship between a character, a book, and a house to verify a fact about Westeros or Essos.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
019e5cfbget book
Retrieves specific metadata for a single book in the series.
019e5cfbget character
Retrieves full details and metadata for a specific character.
019e5cfbget house
Retrieves full details and metadata for a specific noble house.
019e5cfblist books
Lists all books available in the A Song of Ice and Fire series.
019e5cfblist characters
Lists characters, filterable by name, gender, or culture, in the Ice and Fire universe.
019e5cfblist houses
Lists noble houses of Westeros and beyond, filterable by name, region, or words.
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 An API of Ice And Fire, 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, this Ice And Fire API lets you plug the entire A Song of Ice and Fire universe right into your agent. You can nail down any piece of lore, any character, or any noble house without leaving your workflow.
Cataloging the Books
To see every book in the series, you just run list_books for a full roster of titles. Then, if you need the nitty-gritty on one specific book, you use get_book to pull all its metadata.
Digging into Characters
Need to find a character? You run list_characters and can filter the thousands of people by name, gender, or culture. Once you narrow it down, get_character gives you the full profile—all the titles, the aliases, and who they're related to.
Mapping the Great Houses
Want to trace a noble line? You start with list_houses to browse houses by region or their motto. Then, get_house pulls up a complete profile for that family, including their ancestral seats and words.
Fact-Checking Westeros
Your agent can cross-reference everything. You can check the relationship between a character, a book, and a house to verify a fact about Westeros or Essos. You'll get the details on titles, lineage, and lore straight up.
How Ice And Fire MCP Works
- 1 Subscribe to this server on Vinkius. No complex configuration is needed for this public API.
- 2 Your AI agent calls the appropriate listing tool (e.g.,
list_characters) to narrow down the data set. - 3 You pass the specific ID or filtered name from the list output to a detail tool (e.g.,
get_character) to get the final data payload.
The bottom line is: your agent performs a natural conversation to trigger the right sequence of data calls, giving you structured lore data.
Who Is Ice And Fire MCP For?
Writers, world-builders, and academic researchers need this. If your work requires deep, consistent lore—like generating a story based on specific character lineage or verifying a historical detail about Westeros—this server is for you. Stop guessing facts and start writing with verifiable data.
Needs to quickly verify a character's title, family ties, or a house's motto while drafting a scene. They use get_character to keep their world canon-accurate.
Requires structured data on different noble houses (list_houses) to build out game mechanics, like regional allegiances or unique assets.
Studies complex genealogy or historical lore, using list_characters and get_character to build out accurate relationship graphs.
What Changes When You Connect
- Verify character facts instantly. Use
get_characterto pull specific titles, aliases, and family ties for any character, eliminating lore guesswork. - Build a complete book catalog.
list_booksgives you the whole series list, andget_bookpulls specific metadata like ISBNs and POV characters. - Map out entire noble families.
list_houseshelps you browse houses by region or motto, whileget_housegives you their full history and ancestral seat. - Automate world-building. Your agent can combine tools—running
list_charactersthenget_character—to build a structured knowledge graph for your project. - Reduce manual research time. Instead of leaving your workspace to verify a detail, your AI agent handles the data lookup using
get_houseorget_book.
Real-World Use Cases
Drafting a historical scene
A novelist is writing a scene involving House Lannister. They ask their agent, 'What are the words and seat for House Lannister?' The agent runs list_houses and then uses get_house to pull the region, motto, and seat, letting the author keep writing without interruption.
Researching character connections
A student is mapping out the complex lineage of the Targaryen family. They prompt their agent to find all characters with 'Targaryen' in their culture, using list_characters. Then, they use get_character on specific IDs to gather all family and title details in one go.
Cross-referencing book details
A content creator needs to write a summary of the book A Storm of Swords. They use list_books to confirm the title and then run get_book to retrieve the specific metadata, ensuring their summary is factually correct.
Building a game database
A game developer needs a master list of all known noble houses. They use list_houses to get the primary list, and then run get_house on key houses to pull specific data points (like ancestral weapons) into their application's backend.
The Tradeoffs
Trying to find a character by a vague prompt
Asking the agent, 'Tell me about a cool guy from the North.' The agent can't guess the ID or culture, resulting in an unhelpful error or incomplete list.
→
First, use list_characters and filter by 'The North' culture. Then, use get_character with the specific ID of the person you want details on. Always narrow the scope first.
Assuming a single endpoint covers everything
Trying to get a character's house details by only calling a 'search' tool. This fails because the relationship data needs explicit calls.
→
Use list_houses to find the house first. Then, use get_house to get the official details. If you need a character's details, use get_character.
Overloading the agent with too many parameters
Giving the agent a massive, unstructured list of names and asking it to 'find everything about them.' The agent will likely time out or miss connections.
→
Break it down. First, use list_characters to filter by a limited scope (e.g., 'gender=female'). Then, use get_character on the resulting IDs. Keep the queries tight.
When It Fits, When It Doesn't
Use this server if your work is highly dependent on verifiable, structured lore. You need to check lineage, canonical details, or historical facts about Westeros. Don't use it if you just need general fantasy concepts or creative inspiration—use that for brainstorming. If you need a real-time feed of fictional news, this won't work. If you need to cross-reference a character's title against a specific book's metadata, this is the tool you need. The core loop is always: list the general set (list_houses) -> find the specific item -> retrieve the full details (get_house).
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by An API of Ice And Fire. 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
Lore deep dives shouldn't require jumping between Wikis and APIs.
Today, checking a single character's history means opening a Wikipedia page, cross-referencing a fan wiki for their house, and then opening a book index to confirm the title. It's copy-pasting names and IDs between three different sources just to verify one fact.
With this MCP server, your agent handles the whole flow. You ask, 'What is House Stark's region and what are their words?' and the agent uses `list_houses` then `get_house` to give you a single, structured answer right in your chat window.
An API of Ice And Fire MCP Server: Get structured lore data.
The manual steps—finding the ID, switching contexts, and manually merging the data—are gone. Your agent executes the necessary `list_characters` and `get_character` calls in the background.
You get a single, reliable data packet. It’s not just a list; it's the full, structured context you need to write or analyze.
Common Questions About Ice And Fire MCP
How do I use the list_characters tool? +
You run list_characters and specify filters like 'culture' or 'gender'. This gives you a list of matching characters, which you can then pass to get_character for full details.
What is the difference between get_house and list_houses? +
list_houses gives you an index of all noble houses. get_house requires a specific ID or name and gives you the full, detailed profile for just that one house.
Can I use list_books to find a character's book appearances? +
No. list_books only provides the book catalog. You must use get_book and examine the book's metadata for character listings.
Does get_character need a specific ID? +
Yes. get_character needs a specific character ID. First, you should run list_characters to find the correct ID.
What kind of data can I get from get_house? +
You get comprehensive data including the house's region, its ancestral seat, and its family motto.
When I use list_characters, how do I filter by culture or gender? +
You pass the desired criteria directly into the list_characters tool. You can filter by name, gender, or culture to narrow down the results. For example, asking for all characters of Valyrian culture will pull a specific list.
If I use get_book, what information can I expect to receive? +
The get_book tool returns comprehensive details for a single book entry. Expect data points like the ISBN, the full title, the number of pages, and the POV character associated with that specific volume.
What happens if I pass an invalid ID when calling get_house? +
The system returns a clear error message indicating that the house ID provided doesn't exist in the database. This helps you debug and ensures you use a valid ID for the get_house tool.
How can I find a specific character by their name? +
You can use the list_characters tool and provide the name parameter. The agent will return a list of characters matching that exact name, including their titles and aliases.
Can I filter noble houses by their region or motto? +
Yes! Use the list_houses tool with the region or words parameters to narrow down your search to specific areas like 'The North' or specific house mottos.
How do I get the full details of a specific book if I have its ID? +
Simply use the get_book tool and provide the numeric ID. It will return complete metadata including the ISBN, authors, number of pages, and publisher.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Baserow
Manage no-code databases via Baserow — list tables, query rows, create records and manage schemas from any AI agent.
Azure Cognitive Search
Empower your AI with enterprise retrieval — run full-text search, semantic queries, and inspect cognitive skillsets on your Azure indexes.
LeanCloud
Scalable backend-as-a-service platform — manage data classes, users, and push notifications via AI.
You might also like
Xata (Serverless DB)
Manage your serverless databases via Xata — list organizations, manage projects, branches, and execute SQL queries directly from any AI agent.
BugBug
Test your web application automatically with no-code browser tests that catch regressions before your users do.
AirLabs
Access global aviation data via AirLabs — track real-time flights, search airports and airlines, check schedules, and analyze routes from any AI agent.