Skip to main content
Glama
BibTeX Reference Manager MCP

BibTeX Reference Manager MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
parse_bibliographyA

Read BibTeX, RIS or CSL JSON text and return the entries in one normalized shape: lower case field names, tidy whitespace, bare DOIs, the year filled in from a date, and authors split into "Family, Given". Nothing is sent anywhere. Example: text "@article{k1, AUTHOR = {John Smith and Jane Doe}, title={Deep Learning for Graphs}, year={2024}}" returns one entry with authors ["Smith, John", "Doe, Jane"] and lower case field names. Leave format out unless auto picks the wrong one.

convert_bibliographyA

Convert a reference list between BibTeX, RIS, CSL JSON and plain text (a simple reference list style, APA by default, or MLA, IEEE, Chicago or Harvard when you pass style). The input format is detected unless you pass it. Page ranges, DOIs and names are cleaned on the way. Example: text is a BibTeX entry and to is "ris", and output is the same reference as RIS. Set from only to override detection.

dedupe_entriesA

Find duplicate references by matching DOI, by the same cite key, and by similar titles (the years must not clash). Each group says which entry to keep, the one with the most fields, and which to remove. Also returns the list as BibTeX with the extra copies dropped. Example: two entries with the same DOI, one with 3 fields and one with 6, give one group that keeps the entry with 6 fields and lists the other under remove. Your files are not changed.

lint_entriesA

Check a reference list for problems: missing required fields for the entry type, bad page ranges, titles that are not capitalized, invalid DOIs, odd years, repeated keys and unescaped &, %, _ or # in titles, journal names and other text fields (rule unescaped-character). Each issue names the entry key, the field and a plain message. Example: an @article with no journal field gives an issue with the rule missing-field and the field journal. Pass the whole list as text so repeated keys can be found.

fix_entriesA

Apply the safe fixes that lint_entries points to and return the cleaned list as BibTeX: page ranges with one hyphen get a double hyphen, titles that start with a lower case letter or are all lower case get capitals (words inside braces are left alone, and acronyms like DNA, NASA or iOS in those titles are wrapped as {DNA} so BibTeX keeps their case; they are listed in protected_titles), and DOIs written as a link or with a doi: prefix become bare DOIs. Missing fields, backwards page ranges and DOIs that are not valid are not guessed, so run lint_entries on the result. Example: pages "12-15" becomes "12--15". Your files are not changed.

generate_cite_keysA

Create consistent cite keys from the first author's family name, the year and the first meaningful word of the title, like smith2024deep. Repeated keys get a letter added. Returns the old and new key for each entry and the list as BibTeX with the new keys. Example: an entry with key old1, author "Smith, John", year 2024 and title "Deep Learning for Graphs" gives old_key old1 and new_key smith2024deep, or smith2024 when include_title_word is false.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 6 tools

Disambiguation4/5

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.

Naming Consistency5/5

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).

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues