How to integrate Archive.org MCP with Claude Code

Manage your Archive.org directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

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

Manage your Archive.org directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Archive.org with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Archive.org to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

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.

Connecting Archive.org via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Archive.org) for even more tool search precision. It's secure and reliable.

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 step10 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Archive.org account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

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 composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['archive_org'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http archive_org-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Archive.org. This URL will be used to connect Claude Code to Archive.org.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Archive.org
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Archive.org MCP to Claude Code

bash
claude mcp add --transport http archive_org-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (archive_org-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Archive.org MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your archive_org-composio entry in the list
  • This confirms that Claude Code can now access Archive.org tools

If everything is wired up, you should see your archive_org-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Archive.org

The first time you try to use Archive.org tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Archive.org
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Archive.org authorization flow
  • Return to the terminal and start using Archive.org through Claude Code

Once authenticated, you can ask Claude Code to perform Archive.org operations in natural language. For example:

  • "Find Wayback snapshots for example.com"
  • "Download all files for item ABC123"
  • "Retrieve IIIF image manifest for ABC123"

Complete Code

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

import 'dotenv/config';
import { Composio } from '@composio/core';

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 composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['archive_org'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http archive_org-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Archive.org with Claude Code using Composio's MCP server. Now you can interact with Archive.org directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Archive.org operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Archive.org operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

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. Claude Code 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