doc-tools-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@doc-tools-mcpsearch my bibliography for the author 'Smith'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Doc Tools MCP Server
⚠️ Work in Progress — APIs may change without notice.
A Model Context Protocol (MCP) server for managing pandoc/CSL-YAML bibliographies and verifying citations. Lets your LLM read, search, add, update, delete, validate bibliography entries, and systematically verify that citations support the claims made in your text.
Quick Start
npx @metaneutrons/doc-tools-mcpAdd to your MCP client config (e.g., claude_desktop_config.json):
{
"mcpServers": {
"doc-tools": {
"command": "npx",
"args": ["-y", "@metaneutrons/doc-tools-mcp"],
"env": {
"DT_BIB_YAML": "/path/to/references.yaml",
"DT_BIB_CSL": "/path/to/style.csl",
"DT_CT_REGISTRY": "/path/to/ctverify.json"
}
}
}
}Related MCP server: MCP Refchecker
Environment Variables
Variable | Description |
| Default path to CSL-YAML bibliography file. Makes |
| Default path to CSL style file (.csl). Enables style-aware field validation on |
| Default path to citation verification registry JSON. Makes |
All env vars are ignored if the referenced file does not exist. Tool descriptions adapt dynamically to show configured defaults.
Bibliography Tools (bib:*)
Read
Tool | Description |
| Retrieve a single entry by ID (full YAML block) |
| Full-text search across all fields: author, title, type, year, editor, container-title |
| List all entries of a given type (e.g., |
| Check if an ID exists (fast boolean check before citing) |
| Entry count total and breakdown by CSL type |
Write
Tool | Description |
| Add a new entry with duplicate ID check, required field validation, and YAML confirmation output |
| Patch individual fields of an existing entry (other fields remain untouched) |
| Remove an entry by ID |
Validation
Tool | Description |
| Check entire file: YAML syntax, required fields per CSL type, duplicate IDs, missing |
All write operations automatically create a .bak backup before modifying the file.
CSL Style Validation
When a CSL style file is configured (via DT_BIB_CSL or the style parameter), validation uses the variables actually referenced in the style instead of hardcoded required fields. Entry types not handled by the style produce a warning.
Without a style file, these hardcoded defaults apply:
Type | Required Fields |
|
|
|
|
|
|
|
|
|
|
|
|
Citation Verification Tools (ctverify:*)
Systematic verification that cited sources actually support the claims made in the text.
Workflow: extract → set claims → verify each claim against the source → update status.
Tool | Description |
| Extract citations from Pandoc inline footnotes ( |
| Batch update citation entries: set |
| Batch status update by ID list or |
| Show verification progress with counts. Filter by |
Re-sync after edits
Re-running ctverify:extract after text changes is safe:
Exact match — citations with unchanged text keep their claims and status
Proximity match — if cite text changed but the position is within ±5 lines, claims are recovered from the nearest previous entry
dry_run: true— preview new, removed, and proximity-matched entries before committing
Architecture
src/
├── index.ts # MCP server, dynamic provider loading, stdio transport
├── shared/
│ ├── types.ts # Provider, ToolDefinition, ToolResult interfaces
│ ├── logger.ts # Structured logging (pino → stderr)
│ └── errors.ts # Typed error hierarchy
└── providers/
├── bib/ # Bibliography provider
│ ├── index.ts # BibProvider (9 tool handlers, env var resolution)
│ ├── store.ts # YAML read/write with .bak backup
│ ├── schema.ts # Zod schemas + per-type field validation
│ ├── csl-style.ts # CSL style parser (variable extraction per type)
│ └── tools/ # Dynamic tool definitions (read + write)
└── ctverify/ # Citation verification provider
├── index.ts # CtverifyProvider (4 tool handlers)
├── extract.ts # Pandoc inline footnote parser
└── types.ts # CitationEntry interfaceThe provider system is extensible — add a new directory under src/providers/ with a createProvider() export and it will be auto-discovered at startup.
Development
npm install # Install dependencies
npm run build # Compile TypeScript
npm test # Run tests
npm run test:watch # Watch mode
npm run test:coverage # Coverage report
npm run lint # ESLintCommit Convention
This repo uses Conventional Commits enforced via Husky + commitlint.
Types: feat, fix, docs, style, refactor, perf, test, chore, ci, build, revert
Scopes: bib, ctverify, core, deps, config
License
GPL-3.0 — See LICENSE for details.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/metaneutrons/doc-tools-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server