How we check listings

What we list

We list MCP servers, agent skills and plugins that connect AI assistants to traditional engineering software: CAD, BIM, finite element and CFD solvers, geotechnical, power systems, process simulation and similar tools. A listing needs a public home, such as a source repository, a package on a registry like PyPI or npm, or a vendor page. Commercial products are included and labelled as commercial.

We don't list general-purpose servers that happen to touch engineering files unless they are built for an engineering tool.

Where facts come from

• What a listing does, its limitations, supported versions and operating systems come from its own README, documentation or vendor page. If the source doesn't say, we write that it isn't stated rather than guess.
• Install steps are copied exactly from the project's documentation, with a link to where we copied them from.
• Licences come from the project's licence file or package metadata.
• GitHub stars, last update and archived status come from the GitHub API and refresh every night.
• Each listing and tool page shows the date it was last checked and the sources used.

We use directories such as mcp.so, Glama and PulseMCP to find projects, never as the only source for a fact.

What "official" means

A listing is marked official only with evidence: the software vendor publishes it from its own GitHub organisation or package account, or announces it on its own website, or the developers of an open-source tool publish it themselves. Each official listing links to that evidence, and every one is reviewed by a person before it appears. Vendor servers that only answer documentation questions are labelled that way, because they don't operate the software.

What "checked" means, and doesn't

Checked means we read the project's own documentation and recorded what it says, with sources and a date. It doesn't mean we installed and tested every server against every version of the tool, and it isn't a recommendation. Where we have tested something, the page says what and how.

How tool pages are built

Each tool page describes the automation interfaces the software itself exposes, such as a Python API, COM or .NET automation, a command language or text input files, with links to the vendor's documentation. This matters because an MCP server or skill can only do what the tool lets programs do. A server for a tool with a rich API can build and run whole models; one for a tool that only reads input files can prepare and check those files but not drive the user interface.

Each page also records what the vendor itself offers, such as an official MCP server, a built-in assistant or nothing announced, with the date we checked and a source. Related tools are chosen by hand in four groups: alternatives for the same job, tools from the same vendor or API family, tools used next to it in a workflow, and similar tools that don't have integrations yet.

Tools with nothing listed yet

We keep pages for tools that have no MCP server or skill yet, because "nothing exists" is useful to know and those pages invite people to submit or build one. They stay out of search results until they carry enough tool-specific information to be useful on their own: the scripting interfaces with documentation links, the vendor's AI status, what an integration could do, and related tools that do have integrations.

Ordering

Nothing is ranked. Tool pages show official listings first, then community and commercial listings by most recent activity. Archived or missing repositories are shown last with a warning.

How often we refresh

GitHub data refreshes nightly. Every listing and tool is re-checked against its sources at least every six months, and sooner when someone reports a change.

Engineering responsibility

AI-generated models, drawings and results must be checked by a qualified engineer before use. Listing a project here says nothing about whether its output is correct for your work.

Reporting a mistake

Every listing page has a "Suggest an edit" link. You can also use the forms on the submit page.