tia-portal-openness-mcp vs figma
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. figma is a plugin bundle for AI coding tools published by figma. Marketplaces we read that list it: 4 (Claude Code: claude-plugins-official, Official MCP Registry, Claude: knowledge-work-plugins, Copilot CLI: github/awesome-copilot). As of our marketplace pass on 2026-10-23. 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 |  figma | |
|---|---|---|
| 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 |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 2.2.157 Forks (GitHub): 208 Stars (GitHub): 2 101 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 1.0.3 Forks (GitHub): 208 Stars (GitHub): 2 101 Not marked · First seen |
| Claude: knowledge-work-plugins | Not listed | Listed Version: 2.2.157 Forks (GitHub): 208 Stars (GitHub): 2 101 Not marked · First seen |
| Copilot CLI: github/awesome-copilot | Not listed | Listed Version: 2.2.124 Forks (GitHub): 208 Stars (GitHub): 2 101 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 · | figma |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 4 |
| Stars (GitHub) (differs) | 2 | 2 101 |
| Forks (GitHub) (differs) | 0 | 208 |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.figma.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| 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 | 17 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/asckye/tia_portal_openness_mcp | github.com/figma/mcp-server-guide |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago |
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.
figma
Figma design platform integration. Access design files, extract component information, read design tokens, and translate designs into code. Bridge the gap between design and development workflows.
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.
figma As a Claude Code plugin
/plugin install figma@claude-plugins-officialCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only figma has a remote endpoint we check. How we check endpoints
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: figma · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.