tia-portal-openness-mcp vs m-dev-tools
tia-portal-openness-mcp is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
tia-portal-openness-mcp is a plugin bundle for AI coding tools published by asckye. No marketplace we read lists it any more. m-dev-tools is an MCP server published by m-dev-tools. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  m-dev-tools | |
|---|---|---|
| Community marketplace asckye/tia_portal_openness_mcp | Removed on 2026-10-17 Version: 3.3.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.4 Downloads/month (PyPI): 49 Downloads/week (PyPI): 22 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | tia-portal-openness-mcpno longer listed · | m-dev-tools |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 2 | 1 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (m-dev-tools-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/asckye/tia_portal_openness_mcp | github.com/m-dev-tools/m-dev-tools-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of tia-portal-openness-mcp
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Plugin for TIA Portal, TIA Openness API, and Siemens Modular Application Creator workflows
-
TIA Portal MCP gateway: let any AI agent create blocks, write SCL, compile and simulate.
-
Read-only TwinCAT ST intelligence: resolve symbols, library APIs, docs, validate PLC code.
-
mcp-gera-skills io.github.geraservicesuk/mcp-gera-skills
GeraSkills MCP — search and install robot capability packs on behalf of an operator.
-
SkillOS MCP Runtime exposes the SkillOS skill registry as activatable MCP tools for AI agents.
-
festo-codesys-mcp io.github.efranceschetti/festo-codesys-mcp
MCP server for Festo/CODESYS PLCs: IEC 61131-3 ST + validated PLCopen XML generation.
What each says it does
tia-portal-openness-mcp
Siemens TIA Portal Openness automation MCP — runtimes for V14 SP1, V15.1, V16, V17, V18, V19, V20 and V21, plus skills. Selects the newest installed TIA release, then the newest runnable bundled host.
m-dev-tools
MCP server wrapping the m-dev-tools catalog: route_intent, describe, verify.
How to run each
tia-portal-openness-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
m-dev-tools As a local MCP server: PyPI package
claude mcp add --transport stdio m-dev-tools-mcp -- uvx m-dev-tools-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: tia-portal-openness-mcp · What it can do: m-dev-tools · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.