Ext Ops Panel
Open dashboard
Comparison

Session & Memory vs Junê

Session & Memory is a plugin bundle for AI coding tools published by Zhemal Khamidun. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Junê is an MCP server published by Junemind. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-25. 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
MarketplaceSession & MemoryJunê
Community marketplace jhamidun/claude-code-config-pack Listed
Version: 0.1.1
Forks (GitHub): 10
Stars (GitHub): 12
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.8.1
Downloads/month (PyPI): 3 414
Downloads/week (PyPI): 2 493
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.8.1
Downloads/month (PyPI): 3 414
Downloads/week (PyPI): 2 493
Forks (GitHub): 0
Stars (GitHub): 1
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

Session & Memory vs Junê
FactSession & MemoryJunê
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)12 (better)1 (worse)
Forks (GitHub) (differs)10 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (june-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published13, secrets among them: 2
Parts of the bundle (differs)23Not a bundle
Licence (differs)MITLicenseRef-Junemind-EULA
Repository (differs)github.com/jhamidun/claude-code-config-packgithub.com/junemind/june-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-232026-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

Session & Memory

In its own words, on Community GitHub marketplaces:

Memory search/learn, chat history, daily planning, reviews, model switching, session save/restore.

Junê

In its own words, on Official MCP Registry:

Shared, cited knowledge-graph memory for agents — ask, search, remember, keep standing instructions

How to run each

Session & Memory As a Claude Code plugin

Claude Code
/plugin marketplace add jhamidun/claude-code-config-pack
/plugin install session-tools@hamidun

Junê As a local MCP server: PyPI package

Claude Code
claude mcp add --env "JUNE_API_KEY=<YOUR_JUNE_API_KEY>" --env "JUNE_BASE_URL=<YOUR_JUNE_BASE_URL>" --env "JUNE_CANVAS=<YOUR_JUNE_CANVAS>" --env "JUNE_LLM_KEY=<YOUR_JUNE_LLM_KEY>" --transport stdio june-mcp -- uvx june-mcp

Requires: JUNE_API_KEY (secret), JUNE_BASE_URL, JUNE_CANVAS, JUNE_LLM_KEY (secret)

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

The marketplaces of Session & Memory publish no settings it asks for, so we do not compare settings.

What it can do: Session & Memory · What it can do: Junê · Compare two other plugins

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

Where the data comes from: how the catalog is built