Tools

Five tools covering two Internet Archive pillars — Wayback Machine snapshot discovery and retrieval, and IA library search and content access:

ia_find_snapshots

Discover what the Wayback Machine has captured for any URL.

• closest mode: single fast lookup via the Availability API — returns the nearest capture to a given timestamp
• history mode: full capture list via the CDX API, filterable by date range (from/to), HTTP status (status_filter), and MIME type
• Default collapse of timestamp:8 (one capture per day) keeps responses tractable for popular URLs; adjust with the collapse parameter (timestamp:N, N=1–14)
• Resume-key pagination (resume_key) for stepping through large CDX histories without re-scanning

ia_get_snapshot

Retrieve what a page actually said at a point in time.

• Resolves to the nearest available capture when the exact timestamp has no snapshot
• Strips Wayback banner injections and extracts readable text — returns clean content alongside the canonical replay URL for browser access
• Useful for fact-checking, citation verification, and tracing how content changed over time

ia_search_items

Search across 40M+ Archive items by keyword and metadata filters.

• Full-text Solr query syntax plus structured filters: mediatype (texts, audio, video, software, image), collection, creator, language, and date range
• Sort by relevance, date added, or download count
• Pagination via page and rows; output includes total_found and current page/rows so agents can paginate correctly without guessing

ia_get_item

Fetch the complete metadata and file manifest for any Archive item.

• Returns structured fields: title, creator, description, subjects, collections, date, license, and more
• files[] includes every file in the item with its format, size, and direct download URL — the primary way to act on a search result
• metadata response {} on unknown identifier → typed item_not_found error

ia_get_text

Read the OCR text of public-domain books, documents, and transcripts.

• Locates the best available text file in the item's manifest (DjVuTXT preferred, falls back to plain text)
• max_chars and char_offset enable efficient paging through long documents without re-fetching
• Surfaces download_forbidden (HTTP 403) as a typed error for restricted collections rather than failing silently

Resource

All resource data is also reachable via ia_get_item. The resource provides a stable, injectable URI for referencing a specific item across workflows.

Features

Built on @cyanheads/mcp-ts-core:

• Declarative tool, resource, and prompt definitions — single file per primitive, framework handles registration and validation
• Unified error handling — handlers throw, framework catches, classifies, and formats
• Pluggable auth: none, jwt, oauth
• Swappable storage backends: in-memory, filesystem, Supabase, Cloudflare KV/R2/D1
• Structured logging with optional OpenTelemetry tracing
• STDIO and Streamable HTTP transports

Internet Archive-specific:

• No credentials required — all four APIs are public
• Three service layers: WaybackService (Availability + CDX), ArchiveSearchService (Solr), ArchiveMetadataService (Metadata + downloads)
• CDX collapse-by-day default and configurable limit keep responses tractable for high-capture URLs
• Identifies User-Agent on every request as required by IA's terms; configurable via IA_USER_AGENT

Agent-friendly output:

• Pagination context on every list response — total_found, page, rows (search) and resume_key (CDX history) so agents never have to guess whether results are complete
• Typed error reasons (no_snapshots, no_snapshot_available, item_not_found, no_text_file, download_forbidden) with recovery hints so callers can retry or explain to users without parsing text
• Structured file manifests — every ia_get_item response includes file-level metadata (format, size, URL) enabling agents to select the right file without a follow-up call

Getting started

No API key required — the Internet Archive's APIs are fully public.

Add the following to your MCP client configuration file:

{
  "mcpServers": {
    "internet-archive-mcp-server": {
      "type": "stdio",
      "command": "bunx",
      "args": ["@cyanheads/internet-archive-mcp-server@latest"],
      "env": {
        "MCP_TRANSPORT_TYPE": "stdio",
        "MCP_LOG_LEVEL": "info"
      }
    }
  }
}

Or with npx (no Bun required):

{
  "mcpServers": {
    "internet-archive-mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@cyanheads/internet-archive-mcp-server@latest"],
      "env": {
        "MCP_TRANSPORT_TYPE": "stdio",
        "MCP_LOG_LEVEL": "info"
      }
    }
  }
}

Or with Docker:

{
  "mcpServers": {
    "internet-archive-mcp-server": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "MCP_TRANSPORT_TYPE=stdio",
        "ghcr.io/cyanheads/internet-archive-mcp-server:latest"
      ]
    }
  }
}

For Streamable HTTP, set the transport and start the server:

MCP_TRANSPORT_TYPE=http MCP_HTTP_PORT=3010 bun run start:http
# Server listens at http://localhost:3010/mcp

Prerequisites

• Bun v1.3.0 or higher (or Node.js v24+).
• No external accounts or API keys required.

Installation

1. Clone the repository:

git clone https://github.com/cyanheads/internet-archive-mcp-server.git

2. Navigate into the directory:

cd internet-archive-mcp-server

3. Install dependencies:

bun install

4. Configure environment:

cp .env.example .env
# Optional: edit .env for custom User-Agent, timeouts, etc.

Configuration

All configuration is validated at startup via Zod schemas in src/config/server-config.ts.