Ext Ops Panel
Open dashboard
Comparison

Personal Context vs UseMyContext.ai

Personal Context is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). UseMyContext.ai is an MCP server published by usemycontext. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
MarketplacePersonal ContextUseMyContext.ai
Community marketplace danielrosehill/claude-code-plugins Listed
Version: 0.1.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.0
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

Personal Context vs UseMyContext.ai
FactPersonal ContextUseMyContext.ai
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.usemycontext.ai/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)16Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/danielrosehill/claude-personal-context-plugingithub.com/usemycontext/usemycontext
Changes in the last 7 days (differs)20
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 27 h 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

Personal Context

In its own words, on Community GitHub marketplaces:

Builds and maintains a persistent, portable background context layer about the user — intake interview, ingestion of material they already have, gap analysis, scoped retrieval, maintenance and export. Plain markdown entries in a store the user owns, read through declared scopes and sensitivity levels; explicitly does not use model-managed memory. Ships the Portable Context Contract so issue-scoped workspaces can read it without re-asking who the person is.

UseMyContext.ai

In its own words, on Official MCP Registry:

Personal context for AI, written by you and never scraped: your profile and files, any MCP client.

How to run each

Personal Context As a Claude Code plugin

Claude Code
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install personal-context@danielrosehill

UseMyContext.ai As a remote MCP server

Claude Code
claude mcp add --transport http usemycontext https://mcp.usemycontext.ai/mcp

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

Only UseMyContext.ai 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: Personal Context · What it can do: UseMyContext.ai · 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. 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