Ice And Fire MCP. Query Lore Facts for Any Fictional Universe
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 connects a definitive database to your AI agent, letting you query the entire lore of George R.R.
Martin's universe through natural conversation. Need to check character lineage? List every book title or verify a noble house's motto? This MCP gives your agent structured access to thousands of details on Westeros and Essos.
What your AI agents can do
Get book
Retrieves all specific details for one book title in the series.
Get character
Fetches all biographical data for a single character by ID or name.
Get house
Gets all specific details for one noble house, including their words and seat.
It returns a comprehensive list of every book title in the series.
You get metadata for one specific book, including ISBN and page count.
Your agent finds multiple characters using filters like name, gender, or culture.
It fetches all biographical details for one specific individual in the lore.
The agent provides a list of noble families, filtered by region or house name.
You pull specific details about one family's ancestral seat, motto, and region.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
An API of Ice And Fire: 6 Tools
These tools allow you to search the entire database for books, characters, and houses by listing records or retrieving specific details.
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 An API of Ice And Fire on Vinkius019e5cfbget book
Retrieves all specific details for one book title in the series.
019e5cfbget character
Fetches all biographical data for a single character by ID or name.
019e5cfbget house
Gets all specific details for one noble house, including their words and seat.
019e5cfblist books
Pulls an aggregated list of every available book from the A Song of Ice and Fire canon.
019e5cfblist characters
Finds multiple characters, letting you filter the search using criteria like gender or culture.
019e5cfblist houses
Lists multiple noble houses across Westeros and beyond, letting you filter by name or region.
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,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ 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 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.
The Pain of Manual Lore Checks
Right now, if you're writing a piece set in Westeros, you have to context-switch. You open one tab for book data, another for character bios, and a third for house crests. Copying IDs across different pages, cross-checking titles against multiple wikis—it’s slow, tedious, and accuracy is always a gamble.
With this MCP, you feed the question to your agent once. It handles all the data plumbing behind the scenes, executing calls like `list_characters` and fetching specific details with `get_character`. You get clean, structured JSON data back without leaving your workspace.
Getting Specific Lore Data with a Dedicated MCP
You eliminate the need to keep track of six separate functions. Instead of manually searching for 'list' vs 'get', you just ask your agent what data you need, and it uses `list_books` when you want an overview, or `get_book` when you require specific metadata.
The result is predictable: structured facts ready to be inserted into a script or application. The system doesn't guess; it retrieves.
What you can do with this MCP connector
You can connect this database directly to your AI agent, letting it explore the deep lore of A Song of Ice and Fire. Forget sifting through disparate wikis or cross-referencing Wikipedia pages; you ask your agent a question about the Seven Kingdoms, and it finds the facts. Want to know what House Lannister's actual motto is? Need to verify a character’s title from their family line? You get the details instantly.
This MCP lets you pull structured data on books, characters, and noble houses without writing complex SQL queries. Whether you're drafting dialogue for a screenplay or building an application that needs historical lore, your agent handles the retrieval. Because Vinkius hosts this entire catalog of specialized APIs, you connect once and gain access to deep knowledge bases like this one.
019e5cfb-313e-7311-89de-331b5d74bc79 
How Ice And Fire MCP Works
- 1 Subscribe to this MCP via Vinkius. No complex configuration is needed; it’s a public API.
- 2 Connect your preferred AI client (like Cursor or Claude) to the catalog.
- 3 Ask your agent a lore question—for example, 'Who are the characters from Valyrian culture?'—and it runs the necessary tool call.
The bottom line is you ask a natural language question and get structured data back, ready for your next step in the workflow.
Who Is Ice And Fire MCP For?
Screenwriters and fantasy authors who hate Wiki headaches. Historians or gamers needing verifiable lore facts. Developers building educational apps around fictional universes.
Needs to quickly verify a character's exact title, family name, or house motto for consistency across multiple documents.
Must cross-reference names and regions for an essay or paper without leaving their primary research tool.
Integrates high-quality, structured fictional metadata into a prototype application or game backend.
What Changes When You Connect
- You stop guessing. Instead of relying on memory or vague Wiki summaries, you can ask your agent to get a character's full bio using
get_character, guaranteeing accuracy. - Need an overview? Use
list_booksto pull every title in the series instantly, then drill down withget_bookfor specific metadata like ISBNs. - Build out world-building faster. You can list multiple noble houses using
list_housesand immediately check a family's history by runningget_houseon any of them. - It handles the complexity. If you just want to know about Valyrian characters, you call
list_characters, letting your agent filter out irrelevant results for you. - Data integrity is key. You retrieve structured data points—not paragraphs of text—making it simple to use this lore in code or complex documents.
Real-World Use Cases
Checking Character Lineage
A screenwriter needs to confirm if a minor character's title is correct. They ask the agent, which calls list_characters and then uses get_character on the specific ID, confirming the exact lineage before writing the scene.
Cataloging World Lore
A game developer needs a list of all playable factions. They ask for houses in the region, triggering list_houses, then loop through each result, calling get_house to grab the motto and seat for every single one.
Building an Index
A researcher wants a bibliography of all available source material. They use list_books to get titles, then run get_book on each result to compile ISBNs and page counts into a single spreadsheet.
Verifying Cultural Origin
A writer needs to ensure all characters are correctly sourced. They ask for 'all characters from the culture of Essos,' triggering list_characters with the required filter, ensuring no regional errors slip through.
The Tradeoffs
Trying to search everything at once
Telling the agent: 'Tell me about books, characters, and houses.' The agent gets overwhelmed and returns generic information that isn't actionable.
→
Break it down. First, call list_books to get a title. Then, if you need character context for that book, run get_character. Use specific tools for clear results.
Assuming relationship logic
Asking the agent: 'Show me all houses owned by characters from this specific book.' The MCP only provides lookup tools, not complex relational joins.
→
You must first identify the character using get_character, then use that ID to look up their associated house details via get_house.
Mixing listing and detail calls
Asking: 'List houses, but also tell me about House Stark.' The agent might list many houses and then just give one snippet for Stark without the full data packet.
→
Do it in two steps. First, run list_houses to get the overview. Then, run a dedicated call using get_house with the specific house name/ID.
When It Fits, When It Doesn't
Use this MCP if you need verifiable, structured data points from fixed domains: books, characters, or noble houses. If your task involves finding connections (e.g., 'Who fought whom?'), you'll have to execute multiple tool calls sequentially and combine the results yourself.
Don't use it if you just need general knowledge (like a Wikipedia search) or if your data source is unstructured text (like raw manuscripts). For pure semantic searching across massive, undefined datasets, look into vector database tools. However, for guaranteed fact retrieval about Westeros lore, this API is the right choice.
Common Questions About Ice And Fire MCP
How do I find all the books in A Song of Ice and Fire using list_books? +
Just call list_books. This tool pulls an aggregated catalog, giving you titles like 'A Game of Thrones' and their associated metadata for a full overview.
Does get_character allow me to search by gender or culture? +
No. To filter characters, you must use the list_characters tool. This function accepts filters like name, gender, and culture, narrowing down your results before you need a specific character ID.
What is the difference between list_houses and get_house? +
Use list_houses when you want an overview of many families or regions. Use get_house when you know the name of a specific house and need all their detailed lore, like their ancestral weapon.
Can I get details for books using get_book? +
Yes. After running list_books to find a title, call get_book with the corresponding ID. This retrieves specific data points such as page count and ISBNs.
How can I use `list_characters` to search for people from a specific culture or region? +
You pass the desired cultural descriptor as a filter parameter. This allows your agent to narrow down thousands of entries, retrieving only characters associated with that specific background across Westeros and beyond.
If I use `get_house` but provide an ID for a house that doesn't exist, what error handling should my agent expect? +
The API returns a standard 'Not Found' status code. Your agent must check for this specific HTTP response before trying to parse the data, which ensures your workflow remains stable even if IDs are incorrect.
Are there any rate limits or performance considerations when running multiple calls using `list_books`? +
The system supports high throughput for typical usage. If you execute extremely large bulk requests, implementing an exponential backoff strategy in your calling agent is best practice to prevent temporary throttling.
When I use `get_book`, how do I find out which characters are designated as POV characters? +
The metadata returned by the get_book tool includes a list of associated character IDs. Your agent uses these specific IDs to then call get_character and pull the full details for those main story voices.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.