4,500+ servers built on MCP Fusion
Vinkius
Library of Congress logo
Vinkius
OpenAI Agents SDK logo

How to Use the Library of Congress MCP in OpenAI Agents SDK

Get raw historical data directly into your OpenAI Agents SDK pipelines with zero manual configuration using this dedicated MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Library of Congress MCP on Cursor AI Code Editor MCP Client Library of Congress MCP on Claude Desktop App MCP Integration Library of Congress MCP on OpenAI Agents SDK MCP Compatible Library of Congress MCP on Visual Studio Code MCP Extension Client Library of Congress MCP on GitHub Copilot AI Agent MCP Integration Library of Congress MCP on Google Gemini AI MCP Integration Library of Congress MCP on Lovable AI Development MCP Client Library of Congress MCP on Mistral AI Agents MCP Compatible Library of Congress MCP on Amazon AWS Bedrock MCP Support
MCP Servers - Free for Subscribers
OpenAI Agents SDK

Connect Library of Congress MCP to OpenAI Agents SDK

Create your Vinkius account to connect Library of Congress to OpenAI Agents SDK 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

Run targeted historical queries with OpenAI Agents SDK.

The `search` tool executes direct keyword queries against the entire Library of Congress database, passing raw strings straight from your OpenAI Agents SDK loop. You get raw historical records without dealing with manual scraping scripts in your OpenAI Agents SDK workspace. To narrow down the noise, your OpenAI Agents SDK agent uses `search_format` to filter Library of Congress results by maps, photos, or audio. This keeps your OpenAI Agents SDK context window focused strictly on high-value Library of Congress resources.

Extract raw text data using this MCP Server.

The `get_item` tool fetches detailed bibliographic data for any specific asset your OpenAI Agents SDK agent discovers during its Library of Congress search phase. This metadata allows the OpenAI Agents SDK workflow to inspect the exact provenance of old Library of Congress records. For printed Library of Congress materials, your OpenAI Agents SDK workflow calls `get_text_service` to pull full-text OCR, word coordinates, and context snippets. Your OpenAI Agents SDK agent reads these Library of Congress text snippets directly to answer historical questions without downloading huge image files.

Inspect visual assets directly in your agentic workflows.

The `get_image_info` tool retrieves technical IIIF metadata for specific Library of Congress images, giving your OpenAI Agents SDK agent the exact dimensions and tiling details it needs. This avoids blind processing errors when your OpenAI Agents SDK agent handles high-resolution Library of Congress maps. Combine this with `get_resource` so your OpenAI Agents SDK agent can pull discrete digitized files like individual Library of Congress newspaper pages using a specific resource identifier. Your OpenAI Agents SDK agent handles these Library of Congress file endpoints directly, keeping your processing pipeline clean.

Setup guide

Set up Library of Congress MCP in OpenAI Agents SDK

Prerequisites

  • Python 3.10+ installed
  • openai-agents package (pip install openai-agents)
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Install the SDK

    Run pip install openai-agents to install the OpenAI Agents SDK. The MCP integration is built-in — no extra dependencies needed.

  2. 2

    Connect via SSE transport

    Use MCPServerSse with your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. The SDK auto-discovers all Library of Congress tools at runtime.

  3. 3

    Create your Agent

    Pass the MCP to Agent(mcp_servers=[server]). The agent receives Library of Congress tools as native definitions — JSON schemas resolve automatically.

  4. 4

    Run the agent

    Call Runner.run(agent, prompt) to execute. The agent invokes the appropriate Library of Congress tools and returns structured results. Copy the full example on the right to get started.

agent.py
import asyncio
from agents import Agent, Runner
from agents.mcp import MCPServerSse

async def main():
    async with MCPServerSse(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ) as server:
        agent = Agent(
            name="Library of Congress Agent",
            instructions="You have access to Library of Congress tools.",
            mcp_servers=[server],
        )
        result = await Runner.run(agent, "List recent transactions")
        print(result.final_output)

asyncio.run(main())

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.

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 OpenAI Agents SDK

Install the package using pip, then initialize the Library of Congress server with the MCPServerStreamableHttp class pointing to your Vinkius endpoint. Pass this instance in the mcp_servers list when constructing your OpenAI Agents SDK agent to enable automatic tool discovery.
Yes, your OpenAI Agents SDK agent uses the `search_format` tool to restrict results to maps, audio, or photos. This prevents the OpenAI Agents SDK model from wasting tokens on irrelevant file formats from the Library of Congress.
The OpenAI Agents SDK relies on your agent's runtime loop to manage backoff when querying Library of Congress endpoints. You should configure your OpenAI Agents SDK execution policy to handle occasional 429 responses from the Library of Congress gracefully.
Your OpenAI Agents SDK agent calls `get_text_service` with the target resource identifier to retrieve OCR text from the Library of Congress. This allows the OpenAI Agents SDK model to analyze the actual textual content of historical pages directly in its context window.
No, this integration only touches public Library of Congress bibliographic metadata, OCR text, and public-domain image links, keeping your OpenAI Agents SDK queries isolated. Your search terms and retrieved records pass through the Vinkius sandbox, which uses ephemeral execution environments to ensure no OpenAI Agents SDK data is stored.

Start using the Library of Congress MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 8 tools

We've already built the connector for Library of Congress. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 8 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.