metahubdeveloper portal
Free for developers

Publish once.
See how the world uses it.

metahub is the developer portal behind the registry. Paste a GitHub URL, click publish, and end users get your skill / MCP / agent / plugin with one command while you get a live observability dashboard plus star ratings and reviews.

Sign in with GitHubBrowse the registryRead the docs
GitHub-only
No ZIP upload, no key management.
Free tier
Genuinely free. Always.
No SDK code
Telemetry attaches at install.
Open core
MIT licensed, on GitHub.

Three steps, five minutes.

No ZIP signing, no GitHub Actions setup. The repo IS the source of truth. Versioning falls out of git, and the SHA we publish is the SHA your end users install.

Sign in and paste a repo

GitHub Device Flow. No password leaves your browser. Paste a public repo and we read the manifest at the latest commit.

Review the checks

Manifest valid? Slug unique? README present? License declared? A green report unlocks the publish button.

Click publish

We capture the SHA, stamp the artifact verified, and the registry picks it up. End users see it within minutes.

The dashboard

Free observability. Genuinely.

When an end user runs mh install, the CLI attaches a telemetry hook automatically. You see the consequences land in a dashboard you didn't have to write a line of analytics for.

Invocations

24h, 7d, 30d windows. p95 latency. Error rate. Period-over-period deltas.

Top models

Which LLM end users pair with your skill on a given run.

Top tools

Which tool calls your skill triggers: Read, Bash, fs, web.

Handoffs

When your skill ends and another picks up, you see the chain.

Star ratings

Live aggregate + 5-star distribution histogram on every artifact.

Written reviews

Full text, author handle, date. Same panel the registry shows.

Unique installs

Opaque per-machine count. No personally-identifying telemetry.

API key

Rotatable per-artifact key for the SDK. One-click regenerate.

snapshot of a live artifact dashboard

Invocations

2,847

+23%

Unique installs

142

Error rate

0.3%

p95 latency

180 ms

Top models

  • claude-opus-4-7
    1,820
  • claude-sonnet-4-6
    612
  • ollama/llama3.2
    245

Top tools

  • Read
    2,104
  • Bash
    1,430
  • Edit
    980

We don't see what we don't need.

The SDK reports invocation metadata, not content. Your end users keep their prompts, file paths, and tool inputs to themselves.

We report

  • Invocation start, end, status
  • Model used + tools triggered
  • Handoff to another skill
  • Host (claude-code, cursor, ...)
  • Opaque per-install id

We don't

  • Prompt content
  • Tool inputs or outputs
  • File paths or filenames
  • Environment variables
  • The end user's name or email

The portal is for developers. The registry is for everyone.

You publish here. Anyone using Claude Code, Cursor, or Zed installs from the registry. The same artifact, two surfaces.

for developers

The publisher portal

Sign in with GitHub, point at a repo, run the checks, click publish. Every invocation streams back here with the model, tools, handoff target, and any star ratings on the registry.

Sign in
for end users

The catalog at registry.metahub.ai

Browse all four kinds. Star ratings, reviews, freshness signals, install snippets. One terminal command attaches everything to the end user's machine including the telemetry hook.

Browse the registry

Sign in. Paste a repo. Publish.

GitHub Device Flow. No password leaves your browser.

Sign in with GitHubRead the publish guide