Ext Ops Panel
Open dashboard
Comparison

open-ontologies vs codebase-synapse

open-ontologies is a plugin bundle for AI coding tools published by fabio-rovai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). codebase-synapse is an MCP server published by iwiels. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
Marketplaceopen-ontologiescodebase-synapse
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 139
Stars (GitHub): 1 059
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.13
Downloads/month (npm): 229
Downloads/week (npm): 40
Forks (GitHub): 0
Stars (GitHub): 2
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

open-ontologies vs codebase-synapse
Factopen-ontologiescodebase-synapse
Marketplaces that list it11
Stars (GitHub) (differs)1 059 (better)2 (worse)
Forks (GitHub) (differs)139 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (codebase-synapse)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/fabio-rovai/open-ontologiesgithub.com/iwiels/codebase-synapse
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

open-ontologies

In its own words, on Claude Code: claude-plugins-community:

AI-native ontology engineering with 39 MCP tools backed by an in-memory Oxigraph triple store. Build, validate, query, and govern RDF/OWL ontologies using a generate-validate-iterate loop. Supports SPARQL querying, SHACL validation, OWL-RL reasoning, Terraform-style lifecycle management (plan/enforce/apply/monitor/drift), data ingestion from CSV/JSON/XML/XLSX/Parquet, clinical terminology crosswalks (ICD-10, SNOMED CT, MeSH), and ontology alignment with self-calibrating confidence. Written in Rust this is a single binary, no runtime dependencies.

codebase-synapse

In its own words, on Official MCP Registry:

Indexes codebase into a local knowledge graph with 40+ AI tools and codebase-guard.

How to run each

open-ontologies As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install open-ontologies@claude-community

codebase-synapse As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio codebase-synapse -- npx -y codebase-synapse

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: open-ontologies · What it can do: codebase-synapse · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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