Compatible with every major AI agent and IDE
What is the Library of Congress MCP Server?
Connect your AI agent to the Library of Congress (LOC) and explore the vast digital archives of the United States' oldest federal cultural institution. Access millions of records, from historical newspapers to rare maps and sound recordings.
What you can do
- Global Search — Search across the entire LOC catalog including items, legislation, and blogs using the
searchtool. - Digital Collections — Browse and list all available digital collections or drill down into specific ones like the 'Abraham Lincoln Papers' using
list_collectionsandget_collection_items. - Format-Specific Discovery — Filter your research by specific media types such as maps, audio, or photos with
search_format. - Deep Bibliographic Research — Retrieve detailed metadata and digital resource links for specific items using
get_item. - OCR & Text Analysis — Access full-text OCR, word coordinates, and context snippets for digitized documents via
get_text_service. - Technical Image Metadata — Fetch IIIF technical data for high-resolution images using
get_image_info.
How it works
- Subscribe to this server
- Enter your Library of Congress API Key (optional but recommended for higher rate limits)
- Start researching historical data directly from your MCP-compatible client
Who is this for?
- Researchers & Historians — Instantly find primary sources and bibliographic data without manual catalog navigation.
- Educators & Students — Access digitized manuscripts and historical records for curriculum development.
- Data Scientists — Utilize OCR services and metadata for large-scale historical text analysis.
Built-in capabilities (8)
List items within a specific collection
json for a specific image identifier. Get technical metadata about an image (IIIF)
Get detailed bibliographic data for a single item
g., a specific page of a newspaper) using resource_id. Get access to discrete digitized files
Access full-text OCR, word coordinates, and context snippets
List all digital collections
using a keyword query. Search the entire Library of Congress website
g., maps, photos, audio). Search items of a specific format
Why LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Library of Congress through native MCP adapters. Connect 8 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Library of Congress MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Library of Congress queries for multi-turn workflows
Library of Congress in LangChain
Library of Congress and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Library of Congress to LangChain through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Library of Congress in LangChain
The Library of Congress MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 8 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LangChain only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Library of Congress for LangChain
Every tool call from LangChain to the Library of Congress MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I search for items specifically in a format like 'maps' or 'audio'?
Yes! Use the search_format tool and specify the format parameter (e.g., 'maps', 'photos', 'audio') along with your query to get targeted results.
How do I get the full OCR text of a digitized document?
You can use the get_text_service tool. Provide the document segment path and set the full_text parameter to 1 to retrieve the complete OCR transcript.
Can I list items from a specific collection like the Abraham Lincoln papers?
Yes. Use the get_collection_items tool with the collection slug (e.g., 'abraham-lincoln-papers') to see all items contained within that specific archive.
How does LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters
Explore More MCP Servers
View all →
Gmail
12 toolsManage your inbox from AI — read, search, organize, and reply to emails across your Gmail efficiently.

NFe.io
10 toolsOrchestrate NFe.io services — manage service invoices (NFS-e), validate city codes, and monitor company data directly from any AI agent.

Douyin Local Life API / 抖音生活服务
8 toolsChina's leading local life platform — manage shops, process orders, and verify coupons via AI.

Pusher Channels
6 toolsManage real-time communication via Pusher — trigger events, monitor active channels, and manage presence users directly from your AI agent.
