LadDoc Cloud MCP server
Commit Oct 24, 2026Converts ladder-logic documents into TIA Portal importable SimaticML V19 files with strict validation.
Also known as tia-forge/laddoc-cloud, laddoc-cloud
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.1
- Last commit
- Oct 24, 2026
- License
- —
What is LadDoc Cloud MCP?
LadDoc Cloud converts ladder-logic documents into TIA Portal importable SimaticML V19 files with strict validation.
Summary generated from the project's README
About LadDoc Cloud MCP server
LadDoc Cloud provides a remote service for converting ladder-logic documents into SimaticML V19 files for direct import into TIA Portal. This MCP server operates over streamable HTTP using JSON-RPC and requires an API key provided via a Bearer token or X-API-Key header. It is designed for developers working with industrial automation who need to transform LadDoc IR files into functional Siemens PLC blocks like FC, FB, or OB.
The server uses a strict validation gate to ensure reliability. The lad_validate tool checks documents for issues, returning specific error codes and paths, while the lad_generate tool only produces XML if the document passes all checks. This prevents the creation of invalid blocks that would fail during a TIA Portal import. Users can also use the lad_version tool to check the current schema version and bundle hash. The service is stateless and processes one document per call, making it suitable for integration into IDEs like Cursor or command-line tools like Claude Code.
What you can do with it
- 1Verify ladder-logic document integrityCheck a LadDoc document for errors before attempting to generate PLC code.
- 2Convert LadDoc to SimaticMLTransform a validated ladder-logic document into a SimaticML block for TIA Portal.
- 3Prevent symbol mismatchesCompare a document against a project inventory to catch naming errors early.
Written from the project's README. Every use case is checked against a quote from it.
How to install LadDoc Cloud MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall LadDoc Cloud MCP in Claude Code
$ claude mcp add --transport http laddoc-cloud https://tia.hubwiz.com/lad/mcpInstall LadDoc Cloud MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"laddoc-cloud": {
"url": "https://tia.hubwiz.com/lad/mcp"
}
}
}Install LadDoc Cloud MCP in VS Code
.vscode/mcp.json
{
"servers": {
"laddoc-cloud": {
"type": "http",
"url": "https://tia.hubwiz.com/lad/mcp"
}
}
}Install LadDoc Cloud MCP in VS Code CLI
$ code --add-mcp '{"name":"laddoc-cloud","type":"http","url":"https://tia.hubwiz.com/lad/mcp"}'Install LadDoc Cloud MCP in Codex
$ codex mcp add laddoc-cloud --url https://tia.hubwiz.com/lad/mcpInstall LadDoc Cloud MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.laddoc-cloud] url = "https://tia.hubwiz.com/lad/mcp"
Install LadDoc Cloud MCP in Gemini CLI
$ gemini mcp add -s user --transport http laddoc-cloud https://tia.hubwiz.com/lad/mcpInstall LadDoc Cloud MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"laddoc-cloud": {
"url": "https://tia.hubwiz.com/lad/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachabletia-forge/laddoc-cloud is public and reachablegithub.com/tia-forge/laddoc-cloud ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-10-24github.com/tia-forge/laddoc-cloud ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubLadDoc Cloud — LadDoc → SimaticML over MCP
LadDoc Cloud turns a ladder-logic document (LadDoc IR) into SimaticML that TIA Portal imports directly — with a strict validation gate in front of the generator.
This repository is documentation and client configuration only. The service runs at
tia.hubwiz.com; its implementation is not open source.
- Endpoint:
https://tia.hubwiz.com/lad/mcp - Transport: Streamable HTTP (stateless, POST JSON-RPC)
- Auth:
Authorization: Bearer lad_live_…(theX-API-Keyheader is also accepted) - Dashboard / API keys: https://tia.hubwiz.com/lad
- Registry entry:
io.github.tia-forge/laddoc-cloud(official MCP Registry)
What it does
| Tool | Purpose |
|---|---|
lad_version |
Free: returns the LAD-IR identity this service implements (schemaVersion, bundleHash, sourceCommit) |
lad_validate |
Validate one LadDoc document; returns valid plus issues with code / path / message |
lad_generate |
Generate a SimaticML block (FC / FB / OB) — only if validation passes |
Behaviour worth knowing:
- Validation is the gate. One issue and no XML is produced — you never hand TIA Portal a block that cannot be imported. Fix and retry; the remaining issues come back in full.
- Deterministic output. The same LadDoc always produces byte-identical SimaticML;
UIds and connections are assigned by the generator. - Target format: V19 SimaticML documents.
- Optional cross-check: pass the target project's inventory to catch symbol mismatches before generation.
- One document per call: to generate several blocks, call once per block (called FC/FBs are submitted as their own documents).
Quick start
Claude Code
claude mcp add --transport http lad-cloud https://tia.hubwiz.com/lad/mcp \
--header "Authorization: Bearer lad_live_YOUR_KEY"
claude mcp list
Cursor / VS Code / any JSON-configured client
{
"mcpServers": {
"lad-cloud": {
"url": "https://tia.hubwiz.com/lad/mcp",
"headers": { "Authorization": "Bearer lad_live_YOUR_KEY" }
}
}
}
First calls
// free — confirm which LAD-IR bundle this service implements
{ "name": "lad_version", "arguments": {} }
// validate, then generate
{ "name": "lad_validate", "arguments": { "doc": { "schemaVersion": "1.0", "block": { /* … */ } } } }
{ "name": "lad_generate", "arguments": { "doc": { /* same doc */ } } }
Pricing
WeChat login on the dashboard issues a key immediately: 100 calls free. Handshake requests
(initialize, tools/list) and lad_version are free.
Notes
- This service produces text/XML; it does not touch a running TIA Portal. To import the result and compile it, use TIA Portal itself or the on-machine gateway (TiaLink).
- Free companion: PLC Cloud Sim runs the logic before you import it.
- Documentation license: CC BY 4.0. "TIA Portal", "SIMATIC" and "S7" are trademarks of Siemens AG; this service is an independent third-party tool, not affiliated with or endorsed by Siemens.
LadDoc Cloud MCP questions
How do I add LadDoc Cloud MCP to Claude Code?
Run claude mcp add --transport http laddoc-cloud https://tia.hubwiz.com/lad/mcp in your terminal. Add --scope user to make it available in every project.
How do I add LadDoc Cloud MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What happens if my LadDoc document has errors?
The generator will not produce any XML if validation fails; you must fix the issues identified by the validation tool before retrying.
Is the output consistent?
Yes, the service provides deterministic output where the same LadDoc always results in byte-identical SimaticML.