Skip to main content
fastCRW Pergamon
Development

Open VSX Registry

open-vsx.org

The Eclipse Foundation's vendor-neutral open-source registry of VS Code extensions: search extensions, read one extension's metadata, fetch a pinned version record and read its reviews.

Showing the catalogue
Runs on your machine under the source's own terms

The crw MCP on your computer calls Open VSX Registry directly. Calls cost no credits and the data does not pass through fastCRW. Install it once for Claude Code, Cursor, Codex, Windsurf, Gemini CLI or OpenCode, with your fastCRW API key in place of the placeholder:

Ask with this source

A prompt for your agent that names this source and how to call it through the crw MCP.

  • Extension metadata

    Use Open VSX Registry (openvsx) from fastCRW Pergamon, capability "Extension metadata" (extension). You hold a publisher and extension name and want its metadata and available versions. Example options: namespace=ms-python, extension=python. Use the crw MCP tools: crw_find_data to confirm the source and its options, then crw_get_data with provider "openvsx" and capability "extension". Tell me the credits used and cite the licence from the response. If the crw MCP tools are missing, install them with: npx -y crw-mcp install --api-key <your fastCRW API key>

  • Extension version

    Use Open VSX Registry (openvsx) from fastCRW Pergamon, capability "Extension version" (extension-version). You need the record for a pinned version rather than the latest release. Example options: namespace=ms-python, extension=python, version=2024.14.1. Use the crw MCP tools: crw_find_data to confirm the source and its options, then crw_get_data with provider "openvsx" and capability "extension-version". Tell me the credits used and cite the licence from the response. If the crw MCP tools are missing, install them with: npx -y crw-mcp install --api-key <your fastCRW API key>

  • Extension reviews

    Use Open VSX Registry (openvsx) from fastCRW Pergamon, capability "Extension reviews" (reviews). You want user sentiment on an extension before recommending or installing it. Example options: namespace=vscode-icons-team, extension=vscode-icons. Use the crw MCP tools: crw_find_data to confirm the source and its options, then crw_get_data with provider "openvsx" and capability "reviews". Tell me the credits used and cite the licence from the response. If the crw MCP tools are missing, install them with: npx -y crw-mcp install --api-key <your fastCRW API key>

  • Extension search

    Use Open VSX Registry (openvsx) from fastCRW Pergamon, capability "Extension search" (search). You want to find VS Code extensions by keyword across publishers. Example options: query=rust, size=20, offset=0. Use the crw MCP tools: crw_find_data to confirm the source and its options, then crw_get_data with provider "openvsx" and capability "search". Tell me the credits used and cite the licence from the response. If the crw MCP tools are missing, install them with: npx -y crw-mcp install --api-key <your fastCRW API key>