Design
schematex.js.org
Provides tools to discover, validate, and render Schematex diagram DSL into SVG diagrams.
ENDPOINT 1
https://schematex.js.org/mcp
MCP server metadata
- Name
- schematex
- Version
- 1.0.0
Known tools 8
listDiagramsList every Schematex diagram type with selection guidance, standards, aliases, and canvas-editing capabilities.
Inferred read-onlyvalidateDslValidate DSL and return structured line, column, message, and repair hints.
Potential side effectsgetDiagramCapabilitiesReturn the safe canvas text and position-editing model for one diagram type.
Inferred read-onlyinspectDiagramParse existing DSL and return stable editable targets, visible labels, bounds, and allowed edit modes.
Potential side effectsapplyDiagramEditsApply a batch of label or position edits to an inspected diagram revision.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.schematex]
url = "https://schematex.js.org/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"schematex": {
"type": "http",
"url": "https://schematex.js.org/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: schematex
Remote MCP URL: https://schematex.js.org/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"schematex": {
"url": "https://schematex.js.org/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"schematex": {
"type": "http",
"url": "https://schematex.js.org/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "schematex",
"transport": "streamable-http",
"url": "https://schematex.js.org/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.