How to Use the Library of Congress MCP in CrewAI

Q: How do I set up a search task for the Library of Congress in CrewAI?

You pass the server URL directly to your agent's mcps parameter. Then, you simply tell the agent to use the search tool to find specific historical items.

Q: Is it possible to filter which tools my CrewAI agents see for the Library of Congress?

Yes, you use the toolfilter option to restrict access. This ensures your agents only use the tools they need, keeping your crew focused and efficient.

Run autonomous research crews on the Library of Congress using this MCP Server and the CrewAI multi-agent framework.

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 CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Specialized agent collaboration

Assign one agent to `search` for manuscripts while another uses `get_item` to catalog the findings. By splitting the work, your crew processes large collections much faster than a single agent. This leverages the shared memory of your crew. One agent finds the resource, and the next one extracts the relevant details for your final report.

Autonomous archival monitoring

Set a monitor agent to watch for new items using `list_collections`. When it spots a change, it triggers a second agent to use `get_resource` and pull the data. This keeps your research current. You build the crew once, and it maintains your collection as new items hit the digital archives.

Hierarchical document analysis

Use a moderator agent to evaluate the text returned by `get_text_service`. If the content is relevant, it tells the worker agents to grab the full bibliographic data with `get_item`. This creates a smart filtering system. Your crew ignores the noise and only brings you the high-value historical records you actually need.

Setup guide

Set up Library of Congress MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Library of Congress tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Library of Congress Analyst",
    goal="Access and analyze Library of Congress data via MCP.",
    backstory="Expert analyst with direct Library of Congress access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Library of Congress transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Library of Congress Analyst",
        goal="Access and analyze Library of Congress data via MCP.",
        backstory="Expert analyst with direct Library of Congress access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Library of Congress transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

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 CrewAI

You pass the server URL directly to your agent's `mcps` parameter. Then, you simply tell the agent to use the `search` tool to find specific historical items.

Yes, CrewAI agents use shared memory to pass findings between them. One agent can perform the initial `search`, and another can immediately act on those results using `get_item`.

It integrates perfectly. You can assign the server tools to specific agents in your hierarchy, ensuring that only the right roles can access sensitive or high-bandwidth tools.

Yes, you use the `tool_filter` option to restrict access. This ensures your agents only use the tools they need, keeping your crew focused and efficient.

The server uses a zero-trust architecture. It only processes the specific historical metadata requested by your crew and operates in a sandboxed environment that prevents unauthorized data access.

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