// DEPLOYMENT CONFIG VALIDATION
MSI CONFIG
VALIDATOR.
Premier
v1.0.0
Login Required
MCV validates deployment Config XML files against the PRM MSI XSD schema — the same schema
used by the original C# ConfigFileManager tool.
Paste your XML, click Validate, and get line-numbered errors, schema warnings, and a parsed
summary of all Jira tickets and deployment files referenced in the document.
Built for deployment engineers and release managers who need to verify ICIS/eCorp configuration
files before executing a production deployment. Results appear instantly via the JSON API —
no page reload, no stored data.
Live
Line-Numbered Errors
// VALIDATION
Paste, Validate, Fix
The tool is a single two-panel screen. Paste your Config XML into the left textarea.
Click Validate XML or press
Ctrl+Enter. The right panel shows the
validation result banner (green for valid, red for invalid), any line-numbered errors,
schema warnings, and the parsed summary of all Deployment elements.
<?xml version="1.0"?>
<Configuration>
<Deployment BackupFolder="/backup/jan">
<Jira
User="jsmith"
JiraNumber="PROJ-4421"
SourceFileName="module.dll"
VersionNumber="2.4.1"
/>
</Deployment>
</Configuration>
RESULTS
✓
VALID — Conforms to PRM XSD schema
PARSED SUMMARY
Backup Folder
/backup/jan
Jira Items
1
File Items
0
Jira #
User
Source File
Version
PROJ-4421
jsmith
module.dll
2.4.1
// ERROR OUTPUT
Line-Numbered Error Detail
When validation fails, every schema error is reported with the exact line number and a
human-readable message from the XSD validator. Schema warnings (non-fatal) appear separately
below errors. The parsed summary still runs even on invalid documents so you can see what
was successfully parsed before the error occurred.
meltuc.tech/mcv/app — validation error state
✗
INVALID — 2 schema errors found
ERRORS
Line 7
Element 'Jira', attribute 'SequenceNumber': '99999' is not a valid value of the atomic type 'xs:string'.
Line 12
Element 'UnknownTag': This element is not expected. Expected is (Jira | File).
WARNINGS (0)
No warnings.
// FEATURES
Built for the PRM Schema
Embedded XSD Schema
The PRM MSI schema is compiled once on first request and cached in memory.
No external schema files to manage or keep in sync.
Line-Numbered Errors
Every validation error includes the exact line number reported by the XSD validator
so you know exactly where to look in the document.
Errors vs Warnings Split
XSD WARNING-level messages are surfaced separately from fatal errors.
Fix the errors first; review warnings at your discretion.
Parse-on-Failure
Even on invalid documents, MCV parses all Jira and File elements it can find
and shows them in a table with all attributes. See what was parsed before the error.
Ctrl+Enter Shortcut
Keyboard-first workflow. Press Ctrl+Enter (or Cmd+Enter on macOS) while in the
textarea to run validation instantly without reaching for the mouse.
Stateless & Secure
No data is written to a database. Entity resolution and network access are
disabled in the XML parser (XXE and billion-laughs hardened).
Load Example
Pre-fills the input with a valid sample deployment document showing the expected
Configuration › Deployment › Jira / File structure.
MCP Exposure
The validation endpoint is declared as the mcv_validate_xml
MCP tool — callable from any MCP-aware client without a browser.
// GET STARTED
Validate Before You Deploy.
Paste your Config XML. Get line-numbered errors, schema warnings, and a parsed
Jira/File summary. Stateless, fast, and secure.
Launch MSI Config Validator