ReviewMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| review.versionA | Return Re:VIEW CLI version (prefers bundle exec). |
| review.tags.listC | Return allowed tags (built-in conservative list; replace with dynamic probe later). |
| review.enforceTags.checkC | Scan .re files for unknown tags using allowlist; returns violations. |
| review.fixIds.planC | Plan auto-fixes for empty/duplicate IDs across all .re files. |
| review.fixIds.applyC | Apply a previously calculated ID-fix plan; creates .bak backups. |
| review.lintC | Run a fast sanity check by compiling each .re to latex and parsing stderr warnings. |
| review.preprocessC | JS preprocessor only - normalizes input and adds metadata |
| review.build-pdf-hybridC | JS→Ruby hybrid pipeline for PDF generation (PDF first priority) |
| review.check-ruby-extensionsC | Verify Ruby extensions (ReviewExtention) are loaded correctly |
| review.test-mapfileC | Test #@mapfile macro with security validation (developer tool) |
| review.security.configC | Get current security configuration (SSOT from ReviewExtention) |
| review.security.validate-mapfileC | Validate mapfile path and content against security policy |
| review.security.compareC | Compare MCP config with ReviewExtention config to ensure SSOT |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools have distinct purposes targeting specific aspects of the Re:VIEW workflow (e.g., PDF generation, Ruby extensions, tag enforcement, ID fixing, linting, preprocessing, security, mapfile testing, version checking). However, review.security.compare and review.security.validate-mapfile could be slightly confused as both involve security validation, though their specific focuses differ (config comparison vs. mapfile validation).
Tools follow a consistent dot-separated naming pattern (e.g., review.build-pdf-hybrid, review.check-ruby-extensions) with clear verb-noun-action structures. Minor deviations include hyphen usage in some names (e.g., build-pdf-hybrid) versus underscores in others (e.g., validate-mapfile), but overall the pattern is predictable and readable.
With 13 tools, the count is well-scoped for a Re:VIEW document processing server. Each tool addresses a specific need in the workflow (e.g., preprocessing, linting, security, PDF generation), and none appear redundant or unnecessary, fitting a typical range for such a domain.
The toolset covers core aspects of Re:VIEW processing including preprocessing, linting, PDF generation, security validation, and tag/ID management. Minor gaps might include tools for advanced editing or collaboration features, but the surface supports essential workflows without dead ends, allowing agents to handle most tasks effectively.