Is the mcp-wsl-setup MCP server actively maintained?

The mcp-wsl-setup MCP server was last committed today and has 1 contributor. Issue health: 50% of issues resolved. AgentRank freshness score reflects real-time maintenance activity.

mcp-wsl-setup MCP Server

Name: kylebrodeur/mcp-wsl-setup
Rating: 3.1 (1 reviews)
Author: kylebrodeur

kylebrodeur/mcp-wsl-setup

Score: 53.3 Rank #58 MCP Server

Are you the maintainer of kylebrodeur/mcp-wsl-setup? Claim this listing →

Fix VS Code MCP server launches in WSL by resolving stable pnpm/node paths (fnm + corepack).

Add AgentRank to Claude Code Discover and compare tools like kylebrodeur/mcp-wsl-setup — your AI finds the right one automatically

Get API Access →

claude mcp add agentrank -- npx -y agentrank-mcp-server

Overview

kylebrodeur/mcp-wsl-setup is a JavaScript MCP server licensed under MIT. Fix VS Code MCP server launches in WSL by resolving stable pnpm/node paths (fnm + corepack). Topics: cli, corepack, fnm, mcp, model-context-protocol, nodejs, pnpm, vscode, wsl.

Ranked #58 out of 129 indexed tools.

Actively maintained with commits in the last week.

Ecosystem

JavaScript MIT

clicorepackfnmmcpmodel-context-protocolnodejspnpmvscodewsl

Score Breakdown

Stars 15% 1

1 stars → early stage

Freshness 25% today

Last commit today → actively maintained

Issue Health 25% 50%

No issues filed → no history to score

Contributors 10% 1

1 contributor → solo project

Dependents 25% 0

No dependents → no downstream usage

npm Downloads N/A

PyPI Downloads N/A

Forks 0

Description Good

License MIT

Weights: Freshness 25% · Issue Health 25% · Dependents 25% · Stars 15% · Contributors 10% · How we score →

How to Improve

Description low impact

Expand your description to 150+ characters for better discoverability

Contributors medium impact

Single-contributor projects carry bus-factor risk — welcoming contributors boosts confidence

Dependents medium impact

No downstream dependents detected yet — adoption by other projects is the strongest trust signal

Badge all embed codes →

Markdown

[![AgentRank](https://agentrank-ai.com/api/badge/tool/kylebrodeur--mcp-wsl-setup)](https://agentrank-ai.com/tool/kylebrodeur--mcp-wsl-setup/?utm_source=badge&utm_medium=readme&utm_campaign=agentrank_badge)

HTML

<a href="https://agentrank-ai.com/tool/kylebrodeur--mcp-wsl-setup/?utm_source=badge&utm_medium=readme&utm_campaign=agentrank_badge"><img src="https://agentrank-ai.com/api/badge/tool/kylebrodeur--mcp-wsl-setup" alt="AgentRank"></a>

Embed Widget docs →

HTML

<script src="https://agentrank-ai.com/embed.js" data-tool="kylebrodeur/mcp-wsl-setup"></script>

Details

Stars: 1
Forks: 0
Open Issues: 0
Closed Issues: 0
Contributors: 1
Dependents: —
Language: JavaScript
License: MIT
Last Commit: today

Matched Queries

"mcp server""mcp-server"

From the README

# mcp-wsl-setup

Fix VS Code MCP server stdio launches when running Node/pnpm inside WSL via fnm.

## Quick Start

```bash
pnpm dlx mcp-wsl-setup
```

Or with npx:

```bash
npx mcp-wsl-setup
```

Run from your WSL terminal. The script auto-detects your fnm/pnpm paths and
rewrites your VS Code user `mcp.json` in place. Reload the VS Code window
afterwards (`Ctrl+Shift+P` → `Developer: Reload Window`).

### VS Code task (optional)

Copy `.vscode/tasks.json` into your project. Then `Ctrl+Shift+P` →
`Tasks: Run Task` → `Fix MCP pnpm path` runs `pnpm dlx mcp-wsl-setup`
without leaving the editor.

---

# Full Documentation

How to run VS Code MCP servers (stdio transport) reliably when your development
environment is WSL but VS Code is a Windows host application.

---

## Table of Contents

1. [Environment Overview](#1-environment-overview)
2. [fnm and Node.js Setup](#2-fnm-and-nodejs-setup)
3. [Shell Configuration](#3-shell-configuration)
4. [The Problem](#4-the-problem)
5. [Root Causes —

Read full README on GitHub →