Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Generate academic citations from DOI, arXiv, titles, or URLs in BibTeX, APA, MLA formats.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"onecite": {
"command": "uvx",
"args": [
"onecite"
]
}
}
}在终端中运行这条命令
claude mcp add onecite -- uvx onecite粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"onecite": {
"command": "uvx",
"args": [
"onecite"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"onecite": {
"type": "stdio",
"command": "uvx",
"args": [
"onecite"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 HzaCode 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.0.11)于13个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Spec Driven Development, Remote Desktop Commander, HotCodePush
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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
只显示了开头部分;其余内容请在仓库中阅读