plcsense
com.plcsensePublished by plcsense.comv1.1.22Updated Oct 24, 2026
Read-only TwinCAT ST intelligence: resolve symbols, library APIs, docs, validate PLC code.
Overview
A local MCP server that gives an assistant read-only TwinCAT Structured Text intelligence: symbol resolution, library API lookup, documentation and PLC code-adj
- What you can do
- Resolve TwinCAT symbols so the assistant can look up what a name refers to in a PLC project or library context. Look up library APIs and related documentation for TwinCAT Structured Text. Validate PLC code against the resolved symbols and APIs. All of this is read-only intelligence; the description lists no tools that edit, build or deploy projects.
- When to use it
- Useful when working with TwinCAT Structured Text code and you want an assistant to check symbol names, library APIs and documentation, or to validate PLC code before changing it. It suits desktop development work on a licensed machine rather than general-purpose tasks.
- Requirements
- Runs as a local process on the user's machine via npx from the npm package @zeugwerk/plcsense, over stdio. Desktop only; not available as a web executable. A licence is needed: the optional PLCSENSE_LICENSE_KEY environment variable activates a licence in one shot, and can be skipped if the machine is already licensed.
Installation
In SourceWeft
- Open plcsense in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Tools
0Version history
1- v1.1.22LatestSep 16, 2026
Score
15% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.