How to Use the Library of Congress MCP in LlamaIndex

Q: How do I index Library of Congress OCR data into LlamaIndex?

Call gettextservice to retrieve the raw OCR text for a specific historical resource. Pass this text directly to your LlamaIndex document ingest pipeline to chunk, embed, and index it.

Q: Can I perform semantic search on Library of Congress collections with LlamaIndex?

Yes, by indexing the metadata returned by listcollections and getcollectionitems. This lets your LlamaIndex agent perform semantic queries over historical collection descriptions.

Index millions of Library of Congress historical records directly into your LlamaIndex vector store for grounded RAG.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Library of Congress MCP to LlamaIndex

Create your Vinkius account to connect Library of Congress to LlamaIndex and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Library of Congress with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build RAG indexes from historical OCR text

The `get_text_service` tool extracts raw OCR text and context snippets from digitized historical newspapers and manuscripts. Your LlamaIndex pipeline ingests this raw text, splits it into nodes, and writes it directly to your vector store. This process grounds your agent in actual archival data, eliminating typical LLM hallucinations. By using this MCP Server, you transform static historical pages into a dynamic, queryable index.

Semantic search over entire collections

The `list_collections` tool retrieves the complete registry of digital collections available in the archive. Your LlamaIndex agent queries this list to identify target repositories before executing deeper searches. Once identified, the agent uses `get_collection_items` to pull all individual item metadata from that specific collection. This structured approach allows you to build hierarchical indexes of entire historical eras.

Index and query high-resolution image metadata

The `get_image_info` tool retrieves IIIF technical metadata for digitized visual assets like historical maps and photos. LlamaIndex stores this structured JSON metadata alongside your text nodes. When your agent needs to reference a physical asset, it calls `get_resource` to fetch the digitized file path. This links your vector search results directly to the high-resolution source files.

Setup guide

Set up Library of Congress MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Library of Congress MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Library of Congress tools.",
)
response = await agent.run("List recent Library of Congress data")

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Library of Congress. 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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Library of Congress now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Library of Congress MCP in LlamaIndex

Call `get_text_service` to retrieve the raw OCR text for a specific historical resource. Pass this text directly to your LlamaIndex document ingest pipeline to chunk, embed, and index it.

Yes, by indexing the metadata returned by `list_collections` and `get_collection_items`. This lets your LlamaIndex agent perform semantic queries over historical collection descriptions.

You should configure your LlamaIndex ingestion pipeline with rate-limiting wrappers. The server passes raw data from endpoints like `get_item` directly, so your client must manage the call frequency.

Yes, initialize the client and pass it to McpToolSpec. This exposes tools like `search` and `search_format` directly to your LlamaIndex agent as executable functions.

No, all query traffic is transient. The Vinkius MCP Server runs in a zero-trust, ephemeral sandbox, meaning your LlamaIndex search parameters and retrieved metadata are never cached or stored on our servers.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript