How to integrate Archive.org MCP with Google ADK

This guide walks you through connecting Archive.org to Google ADK using the Composio tool router. By the end, you'll have a working Archive.org agent that can search collections, download item files, inspect wayback captures, fetch iiif manifests, and manage item metadata through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a Archive.org account through Composio's Archive.org MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Archive.org logoArchive.org
Api Key

Archive.org is the Internet Archive's digital library of websites, books, audio, video, and images. Use it to preserve, explore, and access historical web captures and public-domain media.

26 Tools

Introduction

This guide walks you through connecting Archive.org to Google ADK using the Composio tool router. By the end, you'll have a working Archive.org agent that can search collections, download item files, inspect wayback captures, fetch iiif manifests, and manage item metadata through natural language commands.

This guide will help you understand how to give your Google ADK agent real control over a Archive.org account through Composio's Archive.org MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Archive.org with

TL;DR

Here's what you'll learn:
  • Get a Archive.org account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Archive.org
  • Build an agent that connects to Archive.org through MCP
  • Interact with Archive.org using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

What is the Archive.org MCP server, and what's possible with it?

The Archive.org MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Archive.org account. It provides structured and secure access to archived content, Wayback captures, item records, usage analytics, and account tasks, so your agent can search collections, retrieve files, manage items, inspect activity, and handle reviews on your behalf.

  • Content search and retrieval: Have your agent search Archive.org by keywords and metadata, inspect complete item records, and download public files.
  • Wayback history research: Instruct your agent to find the closest archived version of a web page or list available captures for a website.
  • Item and file management: Direct your agent to check identifier availability, upload, copy, or delete files, update item metadata, and request new derivatives.
  • Images, manifests, and analytics: Let the agent inspect IIIF image details and manifests, render selected image regions, and review item views, history, geography, and referrers.
  • Account tasks and reviews: Have your agent check your account details, monitor catalog tasks and limits, read task logs, and create, update, retrieve, or delete your reviews.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python
2

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.
3

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Archive.org via MCP
  • python-dotenv loads environment variables
4

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file
5

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management
6

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")
What's happening:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP
7

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["archive_org"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration
8

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Archive.org operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls
9

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

Here's the complete code to get you started with Archive.org and Google ADK:

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["archive_org"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Archive.org operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Archive.org with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Archive.org using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Archive.org tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

TOOLS

Supported Tools

Every Archive.org action and event your agent gets out of the box.

Advanced Search Archive.org Items

Search Archive.

Check Identifier Availability

Check whether an Archive.

Check Archive.org Upload Limit

Check whether Archive.

Copy Item File

Copy one Archive.

Delete Item File

Submit asynchronous deletion of one named file from an Archive.

Delete My Archive.org Review

Permanently delete the connected Archive.

Derive Archive.org Item

Queue Archive.

Download Item File

Download one public file from an Archive.

Find Wayback Snapshots

Find the closest archived Wayback Machine snapshot for each requested URL, using one before, after, or either direction for the batch.

Get Connected Archive.org User

Return the authenticated Archive.

Get Detailed Archive.org Views

Get bounded geographic view analytics and, for items, top referrers over a recent window or date range.

Get IIIF Image Info

Get normalized IIIF Image API capabilities through Archive.

Get IIIF Manifest

Get a compact IIIF Presentation manifest for an Archive.

Get Item Metadata

Get an Archive.

Get Item View Counts

Get all-time, last-30-day, and last-7-day view counts for one or more Archive.

Get Item View History

Get a bounded daily view history for one Archive.

Get My Review

Get the connected Archive.

Get Archive.org Task Log

Download a plain-text log for a task visible to the connected account.

Get Task Rate Limits

Report the connected account's current task capacity and in-flight counts for one Archive.

List Archive.org Tasks

Return any documented combination of the connected account's task summary, active catalog, and resource-authorized history, one page at a time.

List Wayback Captures

Return one bounded structured CDX page of Wayback captures for a URL or host.

Render IIIF Image

Render a bounded crop, resize, rotation, quality, and format from a fixed Archive.

Search Archive.org Items

Search Archive.

Update Item Metadata

Apply JSON Patch changes to one Archive.

Upload Item File

Create or replace one file through Archive.

Upsert My Archive.org Review

Create or overwrite the connected Archive.

FAQ

Frequently asked questions

With a standalone Archive.org MCP server, the agents and LLMs can only access a fixed set of Archive.org tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Archive.org and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Google ADK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Archive.org tools.

Yes, absolutely. You can configure which Archive.org scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Archive.org data and credentials are handled as safely as possible.

Start with Archive.org.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Archive.org tool your agent needs.Free to start.

Start building