Server data from the Official MCP Registry
Build a project glossary from supplied code and doc terms, merged, with source links.
About
Build a project glossary from supplied code and doc terms, merged, with source links.
Security Report
glossarygen is a pure local computation server that normalizes and merges caller-supplied term names into a glossary, with no filesystem access beyond reading the CLI input file, no network calls, no shell execution, and no credentials required. The code is clean, strictly validated, and well tested, and the only requested permissions are minimal and consistent with its stated purpose. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.
8 files analyzed · 7 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"glossarygen": {
"command": "npx",
"args": [
"-y",
"@reneturcios/glossarygen@0.1.0"
]
}
}
}Some servers take additional arguments. See the repository for details.
Documentation
View on GitHubFrom the project's GitHub README.
glossarygen
A project accumulates names faster than it accumulates
explanations for them: the same concept shows up as
user_id in the database layer, UserID in an API type,
and "user id" in the docs, and nobody can say whether
those are one term or three. glossarygen settles that
kind of question from facts you already have. You supply
term occurrences — each name exactly as you found it,
where you found it, and a definition when the docs carry
one — and glossarygen hands back a single merged
glossary: one entry per distinct term, with every source
the term was seen in and the definition the docs gave
it, if any. It writes no definitions of its own and
fetches nothing; it only normalizes and merges what you
supplied.
Normalization follows a fixed recipe, in order. First,
every run of underscores or hyphens becomes a single
space. Then camel humps are split: a space goes before an
uppercase letter that follows a lowercase letter or a
digit, and before an uppercase letter that ends an
acronym run and starts a capitalized word, so
HTTPServer becomes HTTP Server. The result is split
on whitespace and every word is lowercased; the words
joined with single spaces form the term's key. That is
why parseHTTPResponse keys as parse http response,
and why user_id and UserID land on the same key,
user id, and merge into one entry.
Each entry shows its term in display form — the key with
its first character uppercased, so parse http response
reads as Parse http response — together with the
distinct sources across all its occurrences, sorted
ascending, and how many occurrences merged into it. The
entry's definition is the first one supplied in your
order among the merged occurrences; an empty-string
definition still counts as supplied and is kept exactly
as given, and when no occurrence supplies one the
definition is null. Entries come back sorted by key,
and the counts report how many occurrences you supplied,
how many distinct terms they merged into, and how many
of those terms carry a definition versus not.
A name made only of separators, like ___, normalizes
to no words at all and is a validation error naming its
path, as are a missing or empty term list, a non-object
occurrence, a missing, empty, or non-string name or
source, and a definition that is present but not a
string. Invalid input produces no partial glossary.
Unknown extra fields are ignored.
CLI
npx @reneturcios/glossarygen build --input args.json
npx @reneturcios/glossarygen --version
args.json contains the full arguments object:
{
"terms": [
{
"name": "user_id",
"source": "src/user.ts"
},
{
"name": "UserID",
"source": "docs/api.md",
"definition": "Stable identifier for a user account."
},
{
"name": "parseHTTPResponse",
"source": "src/http.ts"
}
]
}
The glossary is printed as JSON:
{
"entries": [
{
"term": "Parse http response",
"sources": ["src/http.ts"],
"occurrences": 1,
"definition": null
},
{
"term": "User id",
"sources": ["docs/api.md", "src/user.ts"],
"occurrences": 2,
"definition": "Stable identifier for a user account."
}
],
"counts": {
"supplied": 3,
"distinct_terms": 2,
"with_definition": 1,
"without_definition": 1
}
}
Exit codes: 0 on success, 1 on a runtime error
(including an unreadable or invalid input file, or
invalid input), 2 on a usage error.
MCP server
npx -y @reneturcios/glossarygen mcp
MCP client config:
{
"mcpServers": {
"glossarygen": {
"command": "npx",
"args": ["-y", "@reneturcios/glossarygen", "mcp"]
}
}
}
Tools
-
build_glossary— Build a project glossary from caller-supplied terms: identifier and doc names are normalized and merged, each entry carrying its sources and its supplied definition, if any.terms(array, required, at least 1 item) — the term occurrences to merge, in the caller's order; each item:name(string, required, non-empty) — term as found: an identifier or a doc phrasesource(string, required, non-empty) — where the term was found (a path or link), echoed as the entry's sourcedefinition(string, optional) — a definition found in the docs
Returns
{entries, counts}, whereentriesholds one{term, sources, occurrences, definition}per distinct normalized term, sorted by term key, andcountsis{supplied, distinct_terms, with_definition, without_definition}.
Docker
docker run -i ghcr.io/cloudcorprecords/glossarygen
docker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/glossarygen build --input /w/args.json
Development
npm install
npm run build # tsc -> dist/
npm test # tsx --test test/*.test.ts (pure local, no network)
npm run dev # run the CLI from source
License
MIT — Copyright (c) 2026 Rene Turcios
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
