How to Use the National Archives Catalog MCP in Google ADK

Q: How do I configure the National Archives Catalog in Google ADK?

Install google-adk and create an McpToolset using StreamableHttpServerParameters with your Vinkius URL. Pass this toolset directly to your LlmAgent initialization.

Q: Can Google ADK agents search the National Archives Catalog by specific text?

Absolutely. The agent uses the searchrecordsbytext tool to find documents based on keywords, returning the exact NARA IDs needed for further retrieval.

Q: Can I restrict which National Archives Catalog tools my Google ADK agent uses?

Yes. You can apply a toolnames filter when setting up the MCP toolset. This is useful if you only want the agent to use getannouncements and block write access like createtag.

Feed primary source historical documents directly into your Google ADK agents for deep Gemini analysis.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect National Archives Catalog MCP to Google ADK

Create your Vinkius account to connect National Archives Catalog to Google ADK 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 National Archives Catalog with Google ADK

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Feed NARA documents into Gemini

Gemini's massive context window is useless without dense data. The `search_records` and `get_record_children` tools let your Google ADK agent pull entire hierarchies of historical documents from the US National Archives. You can dump hundreds of primary sources into a single prompt. Have the agent run `search_records_by_text`, extract the raw metadata, and synthesize historical timelines without losing the thread.

Analyze NARA transcriptions with this MCP Server

Handwritten historical records are notoriously hard to parse. The NARA community transcribes them, and your agent can pull that exact text using `get_transcriptions_by_naid` or `search_transcriptions`. Once the agent pulls the transcriptions, it can cross-reference them against your internal datasets in BigQuery. The integration happens naturally. You just pass the `McpToolset` to your `LlmAgent` and let Gemini handle the routing.

Track archival tags and user metadata

Historical research requires understanding how records are classified. Your agent can execute `get_tags_by_naid` to see how public contributors organize specific NARA files. If you need to map out contributor networks, the agent can call `get_user` and `get_contributions_by_userid`. This pulls public account data and contribution histories, letting your enterprise applications analyze how the public interacts with national records.

Setup guide

Set up National Archives Catalog MCP in Google ADK

Prerequisites

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

1

Install Google ADK

Run pip install google-adk to install the Agent Development Kit. MCP support is included via the McpToolset class.
2

Connect via SSE transport

Use McpToolset.from_server() with SseServerParams pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create an LlmAgent

Pass the returned mcp_tools list directly to LlmAgent(tools=mcp_tools). The ADK maps each MCP tool to a native Gemini function call — no manual schema definitions required.
4

Run with any Gemini model

The agent works with any Gemini model (gemini-2.0-flash, gemini-2.5-pro, etc.). Copy the full example on the right to get started with National Archives Catalog tools in your ADK agent.

agent.py

from google.adk.agents import LlmAgent
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import SseServerParams

# Connect to the MCP via SSE
mcp_tools, exit_stack = await McpToolset.from_server(
    connection_params=SseServerParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    )
)

# Create your agent with auto-discovered tools
agent = LlmAgent(
    name="National Archives Catalog_agent",
    model="gemini-2.0-flash",
    instruction="You have access to National Archives Catalog tools via MCP.",
    tools=mcp_tools,
)

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 National Archives Catalog. 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 National Archives Catalog 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 National Archives Catalog MCP in Google ADK

Install `google-adk` and create an `McpToolset` using `StreamableHttpServerParameters` with your Vinkius URL. Pass this toolset directly to your `LlmAgent` initialization.

Absolutely. The agent uses the `search_records_by_text` tool to find documents based on keywords, returning the exact NARA IDs needed for further retrieval.

The NARA API returns paginated results for heavy queries. Your Gemini agent can read the response from `search_records` and automatically adjust its parameters to fetch the next batch of documents.

Yes. You can apply a `tool_names` filter when setting up the MCP toolset. This is useful if you only want the agent to use `get_announcements` and block write access like `create_tag`.

The MCP protocol runs through an ephemeral, zero-trust sandbox. When your Gemini agent pulls transcription text or user comments via `search_comments`, the data flows straight to your Google Cloud environment without persistent storage on our end.

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