Ext Ops Panel
Open dashboard
Comparison

research-to-integration vs phenoworks-mcp

research-to-integration is a plugin bundle for AI coding tools published by Gleb Kalinin. Marketplaces we read that list it: 1 (Community GitHub marketplaces). phenoworks-mcp is an MCP server published by OpenSciML. Marketplaces we read that list it: 1 (PyPI (MCP servers)). As of our marketplace pass on 2026-11-09. 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
Marketplaceresearch-to-integrationphenoworks-mcp
Community marketplace glebis/claude-skills Listed
Version: 1.0.1
Forks (GitHub): 60
Stars (GitHub): 410
Not marked · First seen
Not listed
PyPI (MCP servers) Not listed Listed
Version: 0.5.1
Downloads/month (PyPI): 547
Downloads/week (PyPI): 116
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

research-to-integration vs phenoworks-mcp
Factresearch-to-integrationphenoworks-mcp
Marketplaces that list it11
Stars (GitHub) (differs)410No figure on GitHub
Forks (GitHub) (differs)60No figure on GitHub
Last release (differs)Not published2026-10-27
Where it runs (differs)Installs as a plugin bundleOn your machine (phenoworks-mcp)
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITApache-2.0
Repository (differs)github.com/glebis/claude-skillsgithub.com/opensciml/phenoworks
Changes in the last 7 days (differs)20
First seen (differs)2026-11-072026-10-13

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

research-to-integration

In its own words, on Community GitHub marketplaces:

Research technical approaches, run bounded comparisons, and deliver reusable code with reproducible tests and configurable autonomy.

phenoworks-mcp

In its own words, on PyPI (MCP servers):

Connect AI assistants to PhenoWorks projects, datasets, and analysis pipelines through MCP.

How to run each

research-to-integration As a Claude Code plugin

Claude Code
/plugin marketplace add glebis/claude-skills
/plugin install research-to-integration@glebis-skills

phenoworks-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands 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: research-to-integration · What it can do: phenoworks-mcp · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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.

Where the data comes from: how the catalog is built