Ext Ops Panel
Open dashboard
Comparison

io.github.ariekogan/ateam-mcp vs TiaLink

io.github.ariekogan/ateam-mcp is an MCP server published by ariekogan. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). TiaLink is an MCP server published by tia-forge. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.ariekogan/ateam-mcpTiaLink
Official MCP Registry Listed
Version: 0.1.2
Downloads/month (npm): 2 356
Downloads/week (npm): 1 326
Forks (GitHub): 4
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (npm): 626
Downloads/week (npm): 90
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
npm registry (MCP servers) Listed
Version: 0.4.127
Downloads/month (npm): 2 356
Downloads/week (npm): 1 326
Forks (GitHub): 4
Stars (GitHub): 1
Not marked · First seen
Not listed

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

io.github.ariekogan/ateam-mcp vs TiaLink
Factio.github.ariekogan/ateam-mcpTiaLink
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)1 (worse)3 (better)
Forks (GitHub) (differs)4 (better)0 (worse)
Last release (differs)2026-11-11Not published
Where it runs (differs)Remote server or your machineOn your machine (tialink-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/ariekogan/ateam-mcpgithub.com/tia-forge/tialink
Changes in the last 7 days (differs)50
First seen (differs)2026-10-112026-10-22
Endpoint at the last check (differs)Responded 9 h ago, requires authenticationno remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.ariekogan/ateam-mcp

In its own words, on Official MCP Registry:

Build, validate, and deploy multi-agent AI solutions from any AI environment.

TiaLink

In its own words, on Official MCP Registry:

TIA Portal MCP gateway: let any AI agent create blocks, write SCL, compile and simulate.

How to run each

io.github.ariekogan/ateam-mcp As a remote MCP server

Claude Code
claude mcp add --transport http ateam-mcp https://mcp.ateam-ai.com/mcp

TiaLink As a local MCP server: npm package

Claude Code
claude mcp add --env "TIALINK_TOKEN=<YOUR_TIALINK_TOKEN>" --transport stdio tialink -- npx -y tialink-mcp

Requires: TIALINK_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only io.github.ariekogan/ateam-mcp 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

The marketplaces of io.github.ariekogan/ateam-mcp publish no settings it asks for, so we do not compare settings.

What it can do: io.github.ariekogan/ateam-mcp · What it can do: TiaLink · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built