s1000d-brex-mcp
Related Servers
Alternatives to s1000d-brex-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables an LLM to check S1000D data modules through XML schema validation, BREX rule checks, and reference resolution, returning an evidence-backed combined verification status per data module or across a whole CSDB folder.5222 npmMIT
- AlicenseAqualityCmaintenanceEnables an LLM to build S1000D data modules and publication modules from structured drafts and numbering rules instead of writing XML, verifying results against XSD, BREX and references and applying only unambiguous fixes. It also supports converting experiential manuals, extracting and restoring translatable segments, creating comment modules, and writing nothing by default.6341 npmMIT
- AlicenseAqualityBmaintenanceProvides LLM agents with a toolset for reviewing S1000D technical publications, including XML schema validation, cross-reference and applicability checks, skeleton generation, and AI-suggested fixes.1MIT
- FlicenseNot gradedqualityCmaintenanceProvides reference and pre-flight linting for XBRL Query and Rules Language (XULE), helping LLMs write syntactically sound rules with tools for object model lookup, function catalog, filter syntax, and boilerplate snippets.-
- AlicenseNot gradedqualityBmaintenanceEnables language models to query, inspect, check, and validate XML documents through XPath 1.0 expressions and XSD schemas without loading the full document into a context window. Documents stay on disk while models retrieve exact counts, values, and structural summaries via tool calls.Apache 2.0
- AlicenseAqualityCmaintenanceEnables an LLM to control Solibri through 25 MCP tools, covering model inspection, rule checking, BCF issue handling, presentations, and Autorun batch verification, all restricted to a local workspace.25MIT
TDQS
Scored across 5 tools
The five tools have largely distinct purposes: notation listing, rule explanation, SNS lookup, value lookup, and data module checking. There is some overlap because explain_brex can also surface notation/value rules that list_notations and lookup_value return, but the descriptions make the intended scopes reasonably clear.
All tool names use consistent snake_case and begin with a verb (list_, explain_, lookup_, check_). The pattern is predictable across the set, even though the verbs vary appropriately by action.
Five tools is well-scoped for a BREX-focused MCP server. Each tool has a clear, non-redundant role: notation listing, rule explanation, SNS decoding, value interpretation, and validation.
The surface covers the main BREX workflows: inspecting rules, decoding SNS codes, interpreting values, listing notations, and checking data modules. Minor gaps exist, such as no dedicated way to enumerate all SNS codes or search rules by free text, but these are workable through existing tools.