annas-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANNAS_SECRET_KEY | No | Your Anna's Archive API key. Needed for downloads. | |
| ANNAS_DOWNLOAD_PATH | No | Absolute folder for downloaded files. Needed for downloads. | |
| ANNAS_ACCOUNT_COOKIE | Yes | Your aa_account_id2 cookie from a signed-in Anna's Archive session. Needed for everything. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| article_downloadA | Download a selected paper by exactly one of doi or hash. Saves the file under ANNAS_DOWNLOAD_PATH and returns path and bytes. Optional title and format control its filename. |
| article_searchA | Find a paper by DOI (including DOI URLs), or search journal articles by keywords. DOI lookup returns one paper; keyword search returns one page. Compare metadata before downloading by hash or DOI. |
| book_downloadA | Download the selected book using its hash from search. Saves a verified file under ANNAS_DOWNLOAD_PATH and returns path and bytes. Format sets the extension; it does not convert the file. |
| book_searchA | Search books, textbooks, manuals, and standards by title, author, or topic. Returns one page with hash, format, metadata, and description when available. Pass a selected hash to book_download. |
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
Each tool targets a distinct resource (article vs book) and action (search vs download), so the four tools form a clean 2x2 matrix with no overlap. An agent can unambiguously pick the right tool based on the resource type and whether it needs to find or fetch content.
All four names follow the same noun_action pattern (article_download, article_search, book_download, book_search), with consistent snake_case and identical verb vocabulary across both resources. This makes the set highly predictable and easy to reason about.
Four tools is exactly the minimal complete surface for a search-and-download server spanning two resource types. Each tool earns its place with no redundancy or filler.
The domain is search-and-fetch for articles and books, and both resource types have matching search and download operations, so the full lifecycle is covered. The search tools explicitly feed into the download tools via DOI/hash, leaving no dead ends.