Normalize identifiers and references into auditable BibTeX or CSL-JSON records for research workflows.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We ran the install command below but it didn't respond within our test window β this can mean a slow first-time install rather than a real problem.
uvx oneciteNo response to initialize.
This is an experimental automated check and can have false negatives β missing environment variables, a slow cold install, etc. It doesnβt necessarily mean somethingβs wrong. Last checked 7d ago.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Onecite.
Features β’ Quick Start β’ Privacy & External Services β’ π Advanced Usage β’ πΊοΈ Roadmap β’ π€ Contributing
OneCite is a command-line and Python toolkit that turns messy, mixed-format references β DOIs, PMIDs, arXiv IDs, ISBNs, URLs, and BibTeX fragments β into auditable BibTeX or CSL-JSON records. Strong identifiers follow documented metadata-service routes; ordinary ambiguous plain-text references are returned as candidates for review and are not auto-promoted by process.
AI-assisted writing, automated literature pipelines, and copy-paste research habits produce ever more reference objects in ever more formats β and ever more chances for wrong, fabricated, or mismatched bibliographic data. Reference managers (Zotero), parsers (AnyStyle, GROBID), format converters (Citation.js), and identifier-to-BibTeX helpers (doi2bib, Manubot) each solve one slice of the problem. OneCite targets the under-served step before references enter a manuscript, systematic review, or manager: an auditable normalization layer that routes strong identifiers (DOI, PMID, arXiv, ISBN, URL, data/software DOIs) to the applicable metadata services, completes available metadata, reports unresolved entries, and produces BibTeX or CSL-JSON.
OneCite is not another reference manager, and process does not auto-accept fuzzy title matches. Strong identifiers are resolved through documented source routes; explicitly labelled thesis/dissertation citations have a separate OpenAIRE/BASE route and can fall back to fields parsed from the input. Ordinary ambiguous text is returned as ranked candidates through onecite suggest for human review rather than silently emitted as source-resolved output. That process/suggest separation, together with machine-readable JSON/NDJSON, exit codes, and deterministic offline checks, makes OneCite a scriptable building block for agents, batch jobs, and reproducible reviews rather than a GUI library. Source resolution does not establish that a work is authentic, unretracted, or correctly described by upstream metadata.
| Feature | Description |
|---|---|
| Candidate Suggestions | Search incomplete plain-text references with onecite suggest without promoting them to resolved bibliography output. |
| Multiple Formats | Input .txt/.bib β Output BibTeX or CSL-JSON. |
| 4-stage Pipeline | A 4-stage process (parse β identify β enrich β format) with explicit unresolved entries. |
| Field Completion | Fill available fields returned by metadata sources, such as journal, volume, pages, authors, and abstract. |
| π 7+ Citation Types | Handles journal articles, conference papers, books, software, datasets, theses, and preprints. |
| Input-Routed Lookup | Uses source-specific routes for Crossref, arXiv, PubMed, Semantic Scholar, Google Books, and others. Not every source is queried for every input. |
| Many Identifier Types | Resolves DOI, PMID, arXiv ID, ISBN, GitHub URL, Zenodo DOI, and DataCite DOI inputs. |
| Custom Templates | YAML-based presets that provide a fallback BibTeX entry type when auto-detection is inconclusive. |
Normal process and suggest runs can make input-dependent outbound requests.
For example, DOI resolution sends the DOI to Crossref (and sometimes a
fallback registry); suggest sends citation queries to Crossref, Semantic
Scholar, and arXiv; arbitrary URL input is fetched from the supplied host; and
thesis queries can be sent to OpenAIRE and BASE. Google Scholar is an optional,
scraping-based suggest fallback that is off by default and may be blocked or
challenged by a CAPTCHA.
OneCite does not provide a privacy-compliance guarantee or a persistent cache
of ordinary live responses. Providers, proxies, output files, and logs may
retain data. Review and redact confidential input before use. See
Privacy and external services for the exact
process/suggest routes, transmitted fields, source-health limits, and the
offline benchmark/doctor boundary.
Install and try OneCite in a few steps.
The current public PyPI release is 0.1.1. This working tree documents the
unreleased 0.2.0 candidate, so install from the checkout when verifying
candidate-only behavior:
Create a file named references.txt with your mixed-format references:
Execute the command to process your file and generate a clean .bib output.
Your results.bib file now contains entries of different types.
Use OneCite directly in your Python scripts.
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/onecite)<a href="https://allmcps.com/mcp/onecite"><img src="https://allmcps.com/api/badge/onecite?style=directory" alt="Onecite on AllMCPs" /></a>