citekick
Agentic tools for academic paper search — a CLI and MCP server that query multiple literature sources in one shot.
Why citekick?
Finding papers usually means juggling separate APIs, rate limits, and response formats for every source. citekick unifies them behind a single interface:
- Multi-source search — Query 8 sources in parallel: Semantic Scholar, arXiv, PubMed, Crossref, Europe PMC, OpenReview, DBLP, and OpenAlex.
- CLI + MCP — Use it directly from your terminal (
citekick) or expose it to AI agents as an MCP server (citekick-mcp). - Agent-friendly output — JSON or Markdown results, ready to be consumed by humans or LLMs.
- Response caching — Built-in HTTP cache to stay polite with APIs and speed up repeated queries.
- Configurable defaults — API keys, preferred sources, year ranges, and output format persisted in one TOML file.
Installation
Install the citekick CLI and MCP server globally using uv:
# Install with uv (recommended)
uv tool install citekick
# Or with pip
pip install citekick
CLI Usage
1. citekick search
Search academic literature across multiple sources.
citekick search "attention is all you need" # Search all default sources
citekick search "diffusion models" --sources arxiv,openalex # Restrict to specific sources
citekick search "protein folding" --year-from 2023 --format markdown
citekick search "llm agents" --max-results 20 --no-cache
Tip: the
searchsubcommand is optional —citekick "query"works too.
2. citekick config
Configure API keys and default search settings in ~/.config/citekick/config.toml.
citekick config # Create an empty config file
citekick config --mailto you@example.com # Set contact email (polite-pool access)
citekick config --openalex-api-key KEY --sources arxiv,pubmed
Credentials and optional contact email are read from ~/.config/citekick/config.toml. The [api] values are all optional; missing or empty values leave the corresponding source keyless.
Agent Integration
To use citekick as an MCP server, add this to your agent's MCP config:
{
"mcpServers": {
"citekick": {
"command": "citekick-mcp"
}
}
}
Or using uvx (without prior installation):
{
"mcpServers": {
"citekick": {
"command": "uvx",
"args": ["--from", "citekick", "citekick-mcp"]
}
}
}
Development
# Install hatch
uv tool install hatch
# Run full release check (linting, static typing with mypy, and test suite with coverage)
hatch run release
License
MIT
Metadata
Release files for citekick 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| citekick-1.0.1.tar.gz | 35.2 kB | With provenance | Details for citekick-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| citekick-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for citekick-1.0.1-py3-none-any.whl |
Total release size: 57.3 kB
Release files / citekick-1.0.1.tar.gz
| Download URL | citekick-1.0.1.tar.gz |
|---|---|
| Size | 35.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4ddee78065b35ad410cc6f62c564077bf8c13c4d6cc226b53bdb655be3622a5b
|
|
BLAKE2b-256 checksum How to use checksums |
d55b8fdc269ac29eb8ef3b4cc5adeb65decde53529f0fb60ed48fe2bc7178926
|
| 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 Aug 21, 2026.
Transparency logRelease files / citekick-1.0.1-py3-none-any.whl
| Download URL | citekick-1.0.1-py3-none-any.whl |
|---|---|
| Size | 22.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d1a230e1ac4bc646e160595600677b394397f9d085a0a96e30655c242c8ce775
|
|
BLAKE2b-256 checksum How to use checksums |
a9ff3b9c5796407fdf3cd0e7ebde1830338f83b9612d3f5ac66f6f978b71fd8b
|
| 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 Aug 21, 2026.
Transparency logSecurity for citekick 1.0.1
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for citekick-1.0.1.tar.gz
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 Aug 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.