Install Slycer in Claude Desktop

Claude Desktop’s chat uses Slycer through the Desktop extension, a single .mcpb file. You install the file from Claude Desktop’s settings, type your keys into the extension’s settings, and Claude builds the local copies you ask for. Usually there is no terminal step.

Claude Desktop runs the extension with uv, a Python tool manager. It uses the uv already on your computer, and if it finds none, Claude Desktop downloads uv from GitHub (github.com) when you install the extension. The extension also needs Python 3.9 or later. If your computer has none, uv normally downloads a Python build, from github.com or releases.astral.sh, but Claude Desktop can tell uv to use only a Python already on your computer. If the install then fails, see If the install fails or the extension does not start; the fix there needs a terminal. This route is not yet tested on a computer account with no uv installed.

Steps

You need no account and no sign-in to fetch data.

  1. Download the extension file, slycer.mcpb. The link always gives the latest release. Each release on the Releases page also carries the file under its version number, slycer-<version>.mcpb.
  2. In Claude Desktop, open Settings, then Desktop app, and select Manage next to Extensions. In older versions, open Settings, then Extensions. Open Advanced settings, and under Extension Developer select Install Extension, then pick the file. Claude Desktop shows a preview. Select Install and confirm. Claude Desktop says it needs to fetch a few dependencies, which may take a few minutes the first time. Extension Developer is where Claude Desktop installs an extension from a file you downloaded; you do not need to be a developer to use it, and Claude Desktop installs nothing until you select Install.
  3. In the extension’s settings, type your own key for each source you use that needs one. Each field says which sources it is for and where to get a key. Claude Desktop keeps the keys in your operating system’s keychain. For BLS, type your work e-mail in BLS contact e-mail.
  4. Ask Claude to build the local copies for the sources you use, for example “build the local copies for the Bank of Japan and Spain’s INE”. Claude tells you each copy’s size before it starts.

Before the first request to the IMF, the Philadelphia Fed surveys, TCMB (EVDS), JODI, the Swiss National Bank or the Swiss Federal Statistical Office, Slycer shows that agency’s terms, in a Claude Desktop dialog where it can, otherwise on a page it opens in your browser on your own computer (127.0.0.1), and sends that agency nothing until you accept. The privacy policy says what Slycer keeps.

Some requests give rows that look right and are wrong. Check the plugin README’s Known issues before a figure goes into client work.

Local copies go to the Data folder, .slycer/data in your home folder unless you choose another. CSV and XLSX files go to the Export folder, Documents/Slycer unless you change it.

Signing in for the paid features

Free use needs no sign-in. Fetching data, writing CSV and XLSX files and building local copies are free on your own computer, with your own agency keys where an agency asks for one. Four things need the paid plan or its trial: looking codes up in a crosswalk between code lists, converting a table with one, saving and re-running datasets, and listing or exporting the record of your requests.

  • Claude Desktop: there is nothing to set. The first time you ask for one of the four, Slycer opens its sign-in page in your browser and Claude tells you the code that page shows.

On the sign-in page, type your work e-mail and open the link Slycer e-mails to it, in the same browser; an address with no plan is offered the trial there (see https://slycer.ai/pricing). One sign-in covers every app on the computer, and Slycer renews it by itself while your subscription runs. There is nothing to paste.

Each seat on a plan is a work e-mail address. The subscription’s owner adds and removes the addresses on the account page.

Update

To update Slycer itself, download slycer.mcpb again from the same link and install the new file the same way.

Your local copies are updated apart from Slycer. For some sources, among them Eurostat and the ECB, the OECD, the BIS, the IMF, Statistics Canada, the ONS, INSEE and FRED, Claude fetches the values live from the agency when you ask for data, and uses the local copy only when the agency cannot be reached. The other sources answer from the local copy, so a new release reaches you only when you update it. Ask Claude “show the status of my local copies” to see each copy’s date (Slycer flags one older than 7 days), and “update my local copies” to pick up new releases.

If the install fails or the extension does not start

When Claude Desktop cannot get uv or a Python, the install stops with its “Extension installation failed” dialog, “Couldn’t install extension”, and the error under it. Two causes are known.

The first is a network that blocks github.com, where Claude Desktop gets uv. This happens when you downloaded slycer.mcpb elsewhere, at home or from a colleague, and install it behind an office proxy. Install uv once yourself. uv’s installer downloads uv from releases.astral.sh first and tries github.com only if that fails, so it works on a network that allows astral.sh. On macOS, paste this line into Terminal; on Windows, paste the second line into PowerShell:

Shell
curl -LsSf https://astral.sh/uv/install.sh | sh
PowerShell
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

uv’s own guide, https://docs.astral.sh/uv/getting-started/installation/, lists other ways to install it, such as from PyPI with pip. If your network blocks astral.sh, github.com and PyPI alike, it has to allow one of them before Claude Desktop can run Slycer.

The second is a computer with no Python 3.9 or later, and the error then names Python. Install uv as above, then run this line in a new terminal. It puts a Python where uv finds it.

Shell
uv python install 3.12

To check, open a new terminal and run uv --version; it prints a version number when uv is installed. Then quit and restart Claude Desktop. If Slycer is not listed under Extensions, install the file again.

Check the file

Each release lists the SHA-256 hash of every file in SHA256SUMS, among the release files, and in release/<version>.sha256 in the slycer-plugin repository at the release’s tag. On macOS or Linux, shasum -a 256 slycer.mcpb prints the hash to compare with the line for slycer.mcpb. Each release file also carries a GitHub artifact attestation from the slycer-plugin repository’s release workflow, which gh attestation verify slycer.mcpb --repo hamzaelsiesy/slycer-plugin checks.