OmniArchive-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KeepLink_DB_PATH | No | Where the SQLite file lives | ./data/task.db |
| KeepLink_API_HOST | No | Bind address | 127.0.0.1 |
| KeepLink_API_PORT | No | Port | 19210 |
| KeepLink_LOG_FILE | No | Log file location | ./data/archiver.log |
| KeepLink_LOG_LEVEL | No | Log verbosity | INFO |
| KeepLink_MAX_RETRIES | No | How many times to retry a failed archive | 5 |
| KeepLink_BASE_BACKOFF | No | Base retry delay in seconds (doubles each time) | 60.0 |
| KeepLink_IA_ACCESS_KEY | No | Your IA S3 key (optional, for higher rate limits) | |
| KeepLink_IA_SECRET_KEY | No | Your IA S3 secret | |
| KeepLink_POLL_INTERVAL | No | Seconds between queue polls | 5.0 |
| KeepLink_WORKER_CONCURRENCY | No | How many tasks to process per poll cycle | 1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| archive_urlA | Submit a URL for archiving to the Internet Archive. Returns immediately with a task_id (non-blocking, <50ms). The actual archiving happens asynchronously in the background. Use this to preserve web page evidence during research — pages may change or disappear, so archive early and often. Duplicate submissions within 24 hours are deduplicated automatically. Response fields: task_id (tracking ID), status (always 'pending' for new submissions), url (submitted URL), is_deduplicated (true if an existing task was reused). |
| get_archive_statusA | Check the status of an archive task. Provide either a task_id or a url (at least one required). Status values: 'PENDING' (queued, waiting to be processed), 'PROCESSING' (worker is archiving now), 'SUCCESS' (archived — result_url contains the Wayback Machine link), 'FAILED' (permanent failure after retries exhausted). When status is SUCCESS, use result_url as a permanent citation link. If status is PENDING/PROCESSING, check again after a few seconds. |
| archive_and_citeA | Archive a cited web source AND get back a paste-ready citation in one call. Non-blocking (<50ms): archiving runs in the background. If the URL was already archived within 24h, you get a COMPLETE citation immediately (formatted markdown link to the permanent Wayback Machine URL). Otherwise you get a PENDING citation with a task_id — call get_archive_status with that task_id later to obtain the permanent archived_url and complete the citation. KeepLink does NOT fetch page content or call any LLM; supply the page title yourself if you want it in the citation. Response fields: title, original_url, archived_url, archived_at, task_id, formatted. |
| retry_taskA | Re-queue a permanently FAILED archive task so the background worker processes it again (e.g. after a transient 403/429). Only tasks whose status is 'failed' can be retried; the task is reset to 'pending' with its retry budget refreshed. Returns the task_id and new status ('pending'). If the task is not failed (pending/processing/success) the call is rejected; if the task_id does not exist a not-found error is returned. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
archive_url and archive_and_cite both submit a URL for archiving, so an agent must decide between them; the citation convenience in archive_and_cite is the only real differentiator and descriptions acknowledge the overlap. retry_task and get_archive_status are clearly distinct.
All four names are verb-first snake_case (archive_url, retry_task, get_archive_status, archive_and_cite), which is predictable overall. The compound 'archive_and_cite' deviates slightly from the verb_noun pattern but remains readable.
Four tools fit the narrow URL-archiving domain well: submit, check status, retry, and cite. It is a touch lean but each tool covers a distinct stage of the workflow.
The set covers submission, status polling, retry, and citation, but there is no way to list existing tasks, cancel a pending archive, or batch-submit URLs—notable gaps for managing multiple tasks during research.