Install Slycer in Claude Code, Cursor and other MCP clients

In Claude Code and Cowork the plugin is the easiest route: see Install the plugin. This page is for Claude Code without the plugin, for Cursor, and for any other client that starts a local MCP server over stdio.

Every route on this page runs the same server, slycer mcp, on your computer. The server sends its workflow to the client as instructions, so no other setup file is needed.

Before you start: uv

Slycer installs with uv, a Python tool manager, which fetches a Python for Slycer if your computer has none. If uv --version does not answer in a terminal, install uv (instructions: https://docs.astral.sh/uv/getting-started/installation/):

Shell
curl -LsSf https://astral.sh/uv/install.sh | sh     # macOS and Linux; or: brew install uv
PowerShell
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

If uv --version is still not found, open a new terminal.

Two ways to start Slycer

  • uvx slycer==0.4.0 mcp fetches this release from PyPI and runs it without installing it. The first start takes longer; later starts use the copy in uv’s cache.
  • slycer mcp runs the slycer command once you install it:

    Shell
    uv tool install slycer==0.4.0
    slycer --version

    If slycer is not found after the install, run uv tool update-shell and open a new terminal.

You need the slycer command for slycer setup (keys) and slycer refresh (local copies) in a terminal, whichever way the client starts the server.

Claude Code

In your shell:

Shell
claude mcp add --scope user slycer -- uvx slycer==0.4.0 mcp

--scope user makes Slycer available in every project. Leave it out to add Slycer to the current project only.

Cursor

Add Slycer to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project):

JSON
{
  "mcpServers": {
    "slycer": {
      "command": "uvx",
      "args": ["slycer==0.4.0", "mcp"]
    }
  }
}

With the slycer command installed, "command": "slycer" and "args": ["mcp"] start the same server.

Other MCP clients

Any client that starts a stdio MCP server takes the same command, uvx slycer==0.4.0 mcp or slycer mcp. Add --direct after mcp to expose every source’s own tools as well.

Keys

Most sources need no key. Save the keys for the sources you use once, in a terminal:

Shell
slycer setup        # asks for each key not set yet; Enter skips one
slycer setup fred   # one key; `setup bls` asks for the e-mail and the key

For each key it shows where to register and which sources it is for, reads the key at a hidden prompt, checks it with one small request to the agency and saves it readable only by you. The server reads the saved keys when the client starts it. The plugin README’s Keys section lists every key.

slycer setup never asks for a Slycer licence key: free use needs none, and the paid features use the sign-in below.

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 Code: there is nothing to set. The first time you ask for one of the four, Slycer opens its sign-in page in your browser, or run slycer login in a terminal first.
  • Cowork, Cursor and other MCP clients: a paid request opens the sign-in page the same way, or run slycer login in a terminal.

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.

Local copies

Ask the client 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”. It tells you each copy’s size first. In a terminal, slycer refresh boj inespain does the same, and slycer refresh --dry-run shows what would be built without fetching anything.

Agency terms and known issues

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 the client’s own dialog where it has one, 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.

Update

Change 0.4.0 to the new version in the command or in mcp.json. With the slycer command installed, run uv tool install slycer==<version> for the new version.