Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Generate academic citations from DOI, arXiv, titles, or URLs in BibTeX, APA, MLA formats.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"onecite": {
"command": "uvx",
"args": [
"onecite"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add onecite -- uvx onecitePégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"onecite": {
"command": "uvx",
"args": [
"onecite"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"onecite": {
"type": "stdio",
"command": "uvx",
"args": [
"onecite"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub HzaCode, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.0.11) llegó al registro hace 13 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Python (uv) en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
OneCite Auditable citation normalization for research workflows
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:
# Current stable public release
pip install onecite
python -m pip install -e .
Create a file named references.txt with your mixed-format references:
# references.txt
10.1038/nature14539
arXiv:1706.03762
ISBN:9780262035613
https://github.com/tensorflow/tensorflow
10.5281/zenodo.3233118
arXiv:2103.00020
Smith, J. (2020). Neural Architecture Search. PhD Thesis. Stanford University.
Execute the command to process your file and generate a clean .bib output.
onecite process references.txt -o results.bib --quiet
Your results.bib file now contains entries of different types.
View Complete Output (results.bib)
@article{LeCun2015Deep,
doi = "10.1038/nature14539", title = "Deep learning", author = "LeCun, Yann and Bengio, Yoshua and Hinton, Geoffrey", journal = "Nature", year = 2015, volume = 521, number = 7553, pages = "436-444", publisher = "Springer Science and Business Media LLC", url = "https://doi.org/10.1038/nature14539", type = "journal-article", abstract = "Deep learning allows computational models that are composed of multiple processing layers to learn representations of data with multiple levels of abstraction...", } @inproceedings{Vaswani2017Attention, arxiv = "1706.03762", title = "Attention Is All You Need", author = "Vaswani, Ashish and Shazeer, Noam and Parmar, Niki and Uszkoreit, Jakob and Jones, Llion and Gomez, Aidan N. and Kaiser, Lukasz and Polosukhin, Illia", year = 2017, booktitle = "Advances in Neural Information Processing Systems (NeurIPS)", url = "https://arxiv.org/abs/1706.03762", }
Direct String and Stdin Input
onecite process "10.1038/nature14539"
onecite suggest "Attention is all you need, Vaswani et al., NIPS 2017" echo "10.1038/nature14539" | onecite process -
</details>
🐍 Use as a Python Library
Use OneCite directly in your Python scripts.
from onecite import process_references
result = process_references( input_content="10.1038/nature14539", input_type="txt", template_name="journal_article_full", output_format="bibtex", )
print('\n\n'.join(result['results']))
</details>
💻 CLI Commands & Options
OneCite provides a command-line interface with the following commands and options:
onecite processThe main command for processing references through the OneCite pipeline.
Usage:
onecite process <input_file> [OPTIONS]
Arguments:
input_file - Input file path, - for stdin, or a strong identifier/reference stringOptions:
| Option | Short | Description | Default |
|---|---|---|---|
--input-type | Input format: txt or bib | txt | |
--template | Fallback BibTeX entry-type preset when auto-detection is inconclusive | journal_article_full | |
--output-format | Output format: bibtex or csl-json for downstream tools that consume CSL-JSON | bibtex | |
--output | -o | Output file path (default: stdout) | - |
--quiet | -q | Suppress verbose logging output | False |
--json | Print a stable JSON envelope instead of BibTeX text | False | |
--ndjson | Print newline-delimited JSON events for streaming automation workflows | False | |
--fail-on-unresolved | Return exit code 2 when any entry cannot be resolved | False |
Examples:
# Process a text file
onecite process references.txt -o results.bib
onecite process references.bib
echo "10.1038/nature14539" | onecite process -
onecite process "10.1038/nature14539"
onecite process references.txt --template conference_paper
onecite process references.txt -o results.bib --quiet
onecite process references.txt --json --fail-on-unresolved
onecite process references.txt --ndjson
Solo se muestra el principio; lee el resto en el repo