Anki Addons MCP
An MCP server that gives LLM clients read-only access to the Anki Addons dataset: every addon in the AnkiWeb catalog, enriched with GitHub, Anki Forum and AI-summary and AI-tag data, published as monthly snapshots.
It answers questions such as "which addon does X?", "will it work on Anki 25.02?", "is it maintained?", and "what changed since last month?".
Links
- Anki Addons dataset on HuggingFace
- anki-addons-dataset, the pipeline that builds the dataset
- Developer Guide: running from sources, debugging, tests, architecture, deployment
Use it locally (STDIO)
Requires uv. uvx runs the PyPI package
in an isolated, cached environment; to run a working copy instead, see
Run from sources.
Register the server in Claude Code:
claude mcp add anki-addons -- uvx anki-addons-mcp
Other MCP clients use the same command (uvx anki-addons-mcp) in their server configuration, e.g.:
{
"mcpServers": {
"anki-addons": { "command": "uvx", "args": ["anki-addons-mcp"] }
}
}
The first start downloads the latest snapshot (~15 MB) into the HuggingFace cache. Older snapshots are downloaded on demand by history tools, so the first history question can take a minute.
Use it remotely (Streamable HTTP)
Connect to the hosted instance on the HuggingFace Space by URL:
claude mcp add --transport http anki-addons https://ya-alex-anki-addons-mcp.hf.space/mcp
The Space sleeps after inactivity, so the first request can take a while. To explore the server in a browser, see Debug with the MCP Inspector.
To host your own instance, see Run over HTTP and Deploy to a HuggingFace Space.
Capabilities
Tools (all read-only, every data tool takes an optional snapshot, YYYY-MM-DD or latest):
search_addons, filter_addons, get_addon, get_addon_readme, get_addon_description,
check_compatibility, assess_maintenance, find_similar_addons, list_addons_by_author,
get_addon_history, diff_snapshots, get_statistics, top_addons, list_snapshots, list_tags, and
query_sql (one sandboxed DuckDB SELECT over the addons and tags tables; only offered by SQL-capable
backends). search_addons and filter_addons filter by AI tags with tags and exclude_tags.
Compatibility follows Anki's parsed versions (point versions and the hard/tested/open/unknown kind of the
upper version); filter_addons also filters by anki_version_kind and anki_version_at_least and sorts by
anki_version.
Resources: anki-addons://dataset/readme, anki-addons://dataset/schema,
anki-addons://dataset/anki-versions, anki-addons://snapshots,
anki-addons://snapshots/{snapshot}/metadata, anki-addons://snapshots/{snapshot}/aggregation,
anki-addons://addons/{addon_id} (and /readme, /description, /history),
anki-addons://authors/{github_user}, anki-addons://tags, anki-addons://tags/{tag}.
Prompts: find_addon_for_task, compare_addons, addon_health_report, upgrade_readiness,
monthly_ecosystem_digest, before_you_build, author_portfolio, best_in_category, category_landscape,
anki_release_readiness.
AI summaries and tags in the dataset are LLM-generated; the server labels them as such.
Configuration
CLI flags override environment variables (prefix ANKI_MCP_, also read from .env).
| Variable | Default | Meaning |
|---|---|---|
ANKI_MCP_TRANSPORT |
stdio |
stdio or http |
ANKI_MCP_HOST / ANKI_MCP_PORT / ANKI_MCP_PATH |
127.0.0.1 / 8000 / /mcp |
HTTP binding |
ANKI_MCP_ALLOWED_HOSTS |
[] |
JSON list of Host headers to allow (enables DNS-rebinding protection) |
ANKI_MCP_BACKEND |
hf_parquet |
hf_parquet (HuggingFace Hub) or local_parquet (a local copy) |
ANKI_MCP_HF_REPO_ID / ANKI_MCP_HF_REVISION |
Ya-Alex/anki-addons / main |
Dataset to serve |
ANKI_MCP_DATA_DIR |
Dataset directory for local_parquet (latest/, history/<date>/) |
|
ANKI_MCP_CACHE_DIR |
HF cache | Download cache |
ANKI_MCP_REFRESH_INTERVAL_SECONDS |
3600 |
Check for a new dataset revision; 0 disables |
ANKI_MCP_SQL_ENABLED / _SQL_MAX_ROWS / _SQL_TIMEOUT_SECONDS |
true / 200 / 10 |
query_sql limits |
ANKI_MCP_MAINTENANCE_ACTIVE_DAYS / _STALE_DAYS |
180 / 730 |
Maintenance label thresholds |
ANKI_MCP_LOG_LEVEL |
INFO |
Logs go to stderr |
HF_TOKEN |
Optional HuggingFace token for higher download rate limits (a Space secret) |
Metadata
Release files for anki-addons-mcp 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| anki_addons_mcp-0.3.0.tar.gz | 51.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| anki_addons_mcp-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 102.5 kB
Release files / anki_addons_mcp-0.3.0.tar.gz
| Download URL | anki_addons_mcp-0.3.0.tar.gz |
|---|---|
| Size | 51.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dfc3a4808533d6ee4254a293bc6072ef9de6a4fcef1214cc1d244f74983049d2
|
|
BLAKE2b-256 checksum How to use checksums |
6d297c6a1d54dfa59f1e72d8edc548fe36a34ad0db1d86fab53687ac7935dc5c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency logRelease files / anki_addons_mcp-0.3.0-py3-none-any.whl
| Download URL | anki_addons_mcp-0.3.0-py3-none-any.whl |
|---|---|
| Size | 51.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
68628e66801e1e8c89b6de45f90d647b83f84732e85d3686ce192d35ffe2bf8e
|
|
BLAKE2b-256 checksum How to use checksums |
d89f5772fe42cc780782af959d31b84b153ade1e02b1e36710f376f84849a54c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency log