useVyre Context vs MeetMyAgent
useVyre Context is an MCP server published by gapra. Marketplaces we read that list it: 1 (Official MCP Registry). MeetMyAgent is an MCP server published by studiomeyer.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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
| Marketplace |  useVyre Context |  MeetMyAgent |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.3 Downloads/month (npm): 144 Downloads/week (npm): 25 Forks (GitHub): 3 Stars (GitHub): 7 Not marked · First seen |
Listed Version: 0.3.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
| Fact | useVyre Context | MeetMyAgent |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 7 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-25 |
| Where it runs (differs) | On your machine (@usevyre/mcp-server) | Remote server (meetmyagent.io/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/gapra/usevyre | github.com/studiomeyer-io/meetmyagent-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 days ago, requires a key |
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
useVyre Context
useVyre component context for AI agents — valid props, variants, anti-patterns, and design tokens.
MeetMyAgent
Turn offers into your AI agent. Manage profiles and enquiries; discover providers via hosted OAuth.
How to run each
useVyre Context As a local MCP server: npm package
claude mcp add --transport stdio usevyre-context -- npx -y @usevyre/mcp-serverMeetMyAgent As a remote MCP server
claude mcp add --transport http meetmyagent https://meetmyagent.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only MeetMyAgent 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: useVyre Context · What it can do: MeetMyAgent · Compare two other plugins
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.