BibTeX Reference Manager MCP
Related Servers
Alternatives to BibTeX Reference Manager MCP
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables local validation, normalization, duplicate detection, and cleaning of chemical compound datasets and identifiers through MCP tools, with stdio-only operation and no outbound requests or telemetry.MIT- AlicenseBqualityCmaintenanceEnables locally-first literature research through an MCP host by collecting sources, parsing documents, retrieving evidence, validating citations, and exporting research records in multiple formats.38MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to audit and fix EPUB, Office, OpenDocument, SVG, and WACZ files entirely offline via the Lens-suite CLI tools, returning stable JSON results.MIT
- AlicenseAqualityBmaintenanceMCP server for Zotero 10+. Read and write your library entirely offline through Zotero's native local API. No plugin, no API key, no cloud.28240 npm13MIT
- FlicenseNot gradedqualityCmaintenanceEnables academic integrity auditing, manuscript preparation, literature search, journal formatting, and submission packaging through local MCP tools.-
- AlicenseBqualityBmaintenanceEnables local, offline batch image processing through MCP tools for resizing, converting, compressing, watermarking, and stripping EXIF metadata from files or folders.6MIT
TDQS
Scored across 6 tools
Each tool has a distinct role: parse normalizes, convert changes format, lint reports, fix applies safe repairs, dedupe groups duplicates, generate_cite_keys rewrites keys. The only mild overlap is parse_bibliography vs convert_bibliography, since both ingest and re-emit a list, but descriptions make the difference (normalized shape vs output format) reasonably clear.
Every tool follows a verb_object snake_case pattern (convert_bibliography, parse_bibliography, lint_entries, fix_entries, dedupe_entries, generate_cite_keys). No mixing of casing or style, and the object noun reflects the domain (entries vs bibliography).
Six tools is well-scoped for a reference-manager pipeline: ingest, validate, repair, deduplicate, rekey, and export. Each tool covers a distinct step with no redundant entries, and nothing feels padded.
The lifecycle of cleaning and converting a bibliography is covered (parse, lint, fix, dedupe, keys, convert) with a sensible text-only, no-file-write stance. Minor gaps exist: no merge/add-entry operation and no tool to look up or validate a DOI against a resolver, but agents can work around these with parse plus convert.