Algenta MCP Server vs Ansys MCP Server
Algenta MCP Server is an MCP server published by thyn-ai. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). Ansys MCP Server is an MCP server published by vorobjewsen30-max. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
| Marketplace |  Algenta MCP Server | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.31 Downloads/month (PyPI): 3 329 Downloads/week (PyPI): 543 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.0.0 Downloads/month (PyPI): 211 Downloads/week (PyPI): 84 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 1.0.41 Downloads/month (PyPI): 3 329 Downloads/week (PyPI): 543 Forks (GitHub): 0 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
| Fact | Algenta MCP Server | Ansys MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-10-23 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (ansys-mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/thyn-ai/algenta-sdk | Not stated |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-13 | no 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
Algenta MCP Server
Governed data discovery, exact queries, decisions, simulations, and runtime utilities over MCP.
Ansys MCP Server
MCP server for Ansys engineering simulations — CFD, FEA, meshing, and post-processing. 24 tools.
How to run each
Algenta MCP Server As a remote MCP server
claude mcp add --transport http algenta https://api.algenta.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: ALGENTA_API_KEY (secret), Authorization header
Ansys MCP Server As a local MCP server: PyPI package
claude mcp add --transport stdio ansys-mcp-server -- uvx ansys-mcp-serverCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Algenta MCP Server 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 Ansys MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: Algenta MCP Server · What it can do: Ansys MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.