LAD Render Cloud — SimaticML ladder diagrams over MCP

io.github.tia-forgePublished by GitHub account tia-forgev0.1.0Updated Nov 11, 2026

Cloud renderer: TIA Portal SimaticML (FC/FB/OB, LAD or SCL) into PNG ladder diagrams over MCP.

The publisher's own server: render.ai Presentations

VerifiedStreamable HTTPWeb executableDeveloper ToolsMedia & Design

Overview

AI-generated overview

Remote MCP service that turns a TIA Portal SimaticML block (FC/FB/OB, LAD or SCL) into a PNG ladder diagram an assistant can generate and review.

What you can do
  • Check the renderer's version, supported languages, block types and size limits (free).
  • Render one SimaticML block into a PNG ladder diagram, optionally a single 0-based network and at 1–3x scale.
  • Reject unsupported inputs with explicit errors, such as DB/UDT/tag tables or FBD/GRAPH/STL blocks.
When to use it
Useful when an assistant writes or edits ladder logic and you want to actually see the resulting diagram, especially on a machine without TIA Portal installed. It is for reading and review, not for compiling or commissioning.
Requirements
Remote Streamable HTTP endpoint at tia.hubwiz.com/render/mcp. A bearer API key from the provider's dashboard, sent in the Authorization header (an X-API-Key header is also accepted). Network access; no local runtime.
Before you install
Every render call costs one credit; a new key includes 100 free renders and top-ups are paid, so usage spends money. The API key is a secret and must be kept out of shared configs. Input XML is sent to a third-party cloud service, and the implementation is not open source. Output is for review only and does not replace compiling in TIA Portal.

Installation

In SourceWeft

  1. Open LAD Render Cloud — SimaticML ladder diagrams over MCP in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.tia-forge%2Flad-render-cloud/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lad-render-cloud-simaticml-ladder-diagra": {
      "type": "http",
      "url": "https://tia.hubwiz.com/render/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

LAD Render Cloud — SimaticML → ladder diagram over MCP

LAD Render Cloud renders a TIA Portal SimaticML block (FC / FB / OB) into a PNG ladder diagram — real ladder layout (contacts, coils, timers/counters, branch merges, jumpers, network titles, interface declaration table), not syntax highlighting and not a code screenshot.

Use it so an AI agent's generated ladder logic can actually be looked at, on a machine that has no TIA Portal installed.

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/render/mcp
  • Transport: Streamable HTTP (stateless, POST JSON-RPC)
  • Auth: Authorization: Bearer render_live_… (the X-API-Key header is also accepted)
  • Dashboard / API keys: https://tia.hubwiz.com/render
  • Registry entry: io.github.tia-forge/lad-render-cloud (official MCP Registry)

What it does

ToolPurposeBilling
render_versionFree: renderer version, supported languages / block types, size and input limitsfree
render_simaticmlTake one SimaticML block, return its PNG ladder diagram1 credit

initialize / tools/list / render_version are free; every other tools/call costs 1 credit, and one call submits exactly one block.

Inputs and limits

  • Accepted: FC / FB / OB blocks in LAD or SCL, including blocks where networks mix both.
  • Rejected with an explicit error: GlobalDB / InstanceDB / UDT / tag tables (no ladder diagram to draw) → UNSUPPORTED_DOCUMENT; FBD / GRAPH / STL → UNSUPPORTED_LANGUAGE.
  • Options: network renders a single 0-based network; scale (1–3) enlarges the image.
  • Limits: input XML 4 MiB, MCP request body 8 MiB, image 32,000,000 pixels with no side over 20,000 px, PNG 12 MiB, rate limit 120 requests/minute. Too tall, or scale too large → render one network instead of the whole block.

How to get SimaticML

In TIA Portal: right-click the block → Export → XML. The saved <Document><SW.Blocks.FC|FB|OB>… text is the SimaticML this service expects. No TIA Portal at hand? Render one of the published example XMLs first.

Quick start

Claude Code

bash
claude mcp add --transport http lad-render https://tia.hubwiz.com/render/mcp \  --header "Authorization: Bearer render_live_YOUR_KEY"claude mcp list

Cursor / VS Code / any JSON-configured client

json
{  "mcpServers": {    "lad-render": {      "url": "https://tia.hubwiz.com/render/mcp",      "headers": { "Authorization": "Bearer render_live_YOUR_KEY" }    }  }}

First calls

jsonc
// free — what does this renderer support right now?{ "name": "render_version", "arguments": {} }
// one block → PNG (costs 1 credit){ "name": "render_simaticml", "arguments": { "xml": "<Document>…</Document>" } }
// a single network, 2× larger{ "name": "render_simaticml", "arguments": { "xml": "<Document>…</Document>", "network": 0, "scale": 2 } }

Pricing

PackPricePer render
Free trial (new API key)100 renders—
1,000 renders¥9.90≈ ¥0.0099
5,000 renders¥29.90≈ ¥0.0060
15,000 renders¥69.90≈ ¥0.0047

No subscription, no monthly fee; balance is applied immediately, and render_version / tools/list never consume credits.

Scope

  • Renders text only: it does not connect to TIA Portal, does not read or write a project, and never downloads to a device. For on-premise project work use the TiaLink MCP gateway (https://github.com/tia-forge/tialink) instead.
  • Output is for reading and review — it does not replace compiling the block in TIA Portal or commissioning on site.

Related

Source: README.md at commit 71a1fc5

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestNov 11, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Render integrations