How to integrate Archive.org MCP with Claude Agent SDK

This guide walks you through connecting Archive.org to the Claude Agent SDK 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 Claude Agent SDK 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.

Get started for freeGet a demo
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 the Claude Agent SDK 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 Claude Agent SDK 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

OpenAI Agents SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Archive.org
  • Configure an AI agent that can use Archive.org as a tool
  • Run a live chat session where you can ask the agent to perform Archive.org operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Archive.org account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Archive.org functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Archive.org
  const session = await composio.create(USER_ID, {
    toolkits: ['archive_org'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Archive.org
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Archive.org tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Archive.org
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Archive.org and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['archive_org']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Archive.org tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Archive.org through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
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.

FRAMEWORKS

How to build Archive.org MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Archive.org MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Archive.org MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Archive.org MCP with Claude Cowork

Codex logo

Codex

Use Archive.org MCP with Codex

OpenClaw logo

OpenClaw

Use Archive.org MCP with OpenClaw

Hermes logo

Hermes

Use Archive.org MCP with Hermes

CLI logo

CLI

Use Archive.org MCP with CLI

Google ADK logo

Google ADK

Use Archive.org MCP with Google ADK

LangChain logo

LangChain

Use Archive.org MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Archive.org MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Archive.org MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Archive.org MCP with LlamaIndex

CrewAI logo

CrewAI

Use Archive.org MCP with CrewAI

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. Claude Agent SDK 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
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies