Ext Ops Panel
Open dashboard
Comparison

backpack-ontology vs OntoRamp Graph Query

backpack-ontology is a plugin bundle for AI coding tools published by NoahIrzinger. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). OntoRamp Graph Query is an MCP server published by ontoramp.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
Marketplacebackpack-ontologyOntoRamp Graph Query
Claude Code: claude-plugins-community Listed
Version: 0.7.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
Forks (GitHub): 0
Stars (GitHub): 0
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

backpack-ontology vs OntoRamp Graph Query
Factbackpack-ontologyOntoRamp Graph Query
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (backpack-ontology)Remote server (ontoramp-graph-query.fly.dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)6Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/noahirzinger/backpack-ontology-plugingithub.com/matthewdavisaiarchitect/ontoramp-graph-query
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago

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

backpack-ontology

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

A persistent knowledge graph engine for Claude Code. Gives your AI agent structured, searchable memory that persists across sessions — stored as typed graphs with nodes and edges. Features progressive discovery so the context window stays clean: Claude browses layer by layer, only pulling in what it needs. Supports freeform schemas, full-text search, graph traversal, and bulk operations. Data is stored as human-readable JSON following the XDG specification.

OntoRamp Graph Query

In its own words, on Official MCP Registry:

Architecture-grounded query for AI agents. Governance constraints, evidence-linked answers.

How to run each

backpack-ontology As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install backpack-ontology@claude-community

OntoRamp Graph Query As a remote MCP server

Claude Code
claude mcp add --transport http graph-query https://ontoramp-graph-query.fly.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only OntoRamp Graph Query 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

Neither one's marketplaces publish the settings it asks for.

What it can do: backpack-ontology · What it can do: OntoRamp Graph Query · 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