Library
Skills and MCP plugins for FORGE. Verified entries are reviewed and pinned by sha256, so the file you install is byte-for-byte the file that was reviewed. Community entries are unreviewed. Either way, FORGE keeps their tools behind ask-permission.
Start with the tools people reach for most: browser control, memory, documentation, Git, filesystem, web fetch, GitHub, SQLite and timezone helpers. The six newer entries are listed as Community until they have been booted and reviewed on Windows.
Nobody has read this code or skill text on your behalf. These come straight from the public MCP registry and community submissions. An MCP server runs as your user the moment you connect it, so read the source before installing, exactly as you would any package. FORGE keeps every community tool behind ask-permission: it can never run a call you did not approve.
Loading from the public MCP registry…
Anyone can submit. Every submission lands in the community tier and waits for review; submitting never publishes, and never grants Verified. The full criteria are in REGISTRY.md.
Email kevinklubeck@gmail.com with your entry. The source repository is private while FORGE is in commercial release, so there is no pull request for you to open — a maintainer files it for you.
Send the registry fields — name, what it does, where the code lives, and a
SKILL.md if it is a skill. Anything you link to must be public,
because it gets read before it gets listed.
It lands in community. Only a maintainer can set the verified tier, and a verified skill is always sha256-pinned in the same change.
There
is a submission API (POST /api/registry/submit, token-authenticated),
but it is not open for sign-ups yet: it requires a verified email address and this
deployment has no mail provider configured, so an account created today could
never finish verifying. Rather than show you a form that cannot complete, the
email route above is the one that actually works. The API opens when the
accounts side is finished.
