MCP-Server konfigurieren

Einrichten MCP server connections for Claude Code (WSL) and Claude Desktop (Windows).

Wann verwenden

• Setting up Claude Code to connect to R via mcptools
• Configuring Claude Desktop with MCP servers
• Adding Hugging Face or other remote MCP servers
• Troubleshooting MCP connectivity zwischen tools

Eingaben

• Erforderlich: MCP server type (mcptools, Hugging Face, custom)
• Erforderlich: Client (Claude Code, Claude Desktop, or both)
• Optional: Authentication tokens
• Optional: Custom server implementation

Vorgehensweise

Schritt 1: Installieren MCP Server Packages

For R (mcptools):

install.packages("remotes")
remotes::install_github("posit-dev/mcptools")

For Hugging Face:

npm install -g mcp-remote

Erwartet:

mcptools

installs from GitHub and loads in R ohne errors.

mcp-remote

ist verfuegbar globally via

which mcp-remote

or

npm list -g mcp-remote

.

Bei Fehler: For

mcptools

, ensure

remotes

is installed first. If GitHub rate-limits the install, set a

GITHUB_PAT

in

~/.Renviron

. For

mcp-remote

, verify Node.js and npm are installed and on PATH.

Schritt 2: Konfigurieren Claude Code (WSL)

R mcptools server:

claude mcp add r-mcptools stdio \
  "/mnt/c/Program Files/R/R-4.5.0/bin/Rscript.exe" \
  -- -e "mcptools::mcp_server()"

Hugging Face server:

claude mcp add hf-mcp-server \
  -e HF_TOKEN=your_token_here \
  -- mcp-remote https://huggingface.co/mcp

Verifizieren configuration:

claude mcp list
claude mcp get r-mcptools

Erwartet:

claude mcp list

shows both

r-mcptools

and

hf-mcp-server

(or whichever servers were added).

claude mcp get r-mcptools

displays the correct command and arguments.

Bei Fehler: If der Server nicht appear in the list, verify

~/.claude.json

contains the correct entry. If the

claude

command ist nicht found, add it to PATH:

export PATH="$HOME/.claude/local/node_modules/.bin:$PATH"

.

Schritt 3: Konfigurieren Claude Desktop (Windows)

Edit

%APPDATA%\Claude\claude_desktop_config.json

:

{
  "mcpServers": {
    "r-mcptools": {
      "command": "C:\\PROGRA~1\\R\\R-45~1.0\\bin\\x64\\Rscript.exe",
      "args": ["-e", "mcptools::mcp_server()"]
    },
    "hf-mcp-server": {
      "command": "mcp-remote",
      "args": ["https://huggingface.co/mcp"],
      "env": {
        "HF_TOKEN": "your_token_here"
      }
    }
  }
}

Important: Use 8.3 short paths for Windows directories with spaces (

PROGRA~1

not

Program Files

). Use Umgebungsvariables for tokens, not

--header

arguments.

Erwartet: The JSON config file at

%APPDATA%\Claude\claude_desktop_config.json

is valid JSON with the correct server entries. Claude Desktop shows MCP server indicators nach restart.

Bei Fehler: Validieren the JSON with a linter (e.g.,

jq . < config.json

). Use 8.3 short paths (

PROGRA~1

) if Windows path spaces cause parsing errors. Sicherstellen Claude Desktop is fully restarted (not just minimized).

Schritt 4: Konfigurieren R Session for MCP

Hinzufuegen to project

.Rprofile

:

if (requireNamespace("mcptools", quietly = TRUE)) {
  mcptools::mcp_session()
}

This starts the MCP session automatisch when opening das Projekt in RStudio.

Erwartet: The

.Rprofile

file conditionally starts

mcptools::mcp_session()

when das Projekt is opened in RStudio, making MCP tools available automatisch.

Bei Fehler: If

mcptools

ist nicht found at session start, verify it is installed in the library that RStudio uses (check

.libPaths()

). If using renv, ensure mcptools is in the renv library.

Schritt 5: Verifizieren Connections

Testen R MCP from WSL:

"/mnt/c/Program Files/R/R-4.5.0/bin/Rscript.exe" -e "mcptools::mcp_server()"

Testen from innerhalb Claude Code:

Starten Claude Code and use MCP tools — they should appear in the tool list.

Testen Claude Desktop:

Restart Claude Desktop nach configuration changes. Pruefen auf MCP server indicators in the UI.

Erwartet: Running Rscript with

mcptools::mcp_server()

produces output ohne errors. MCP tools appear in the Claude Code tool list waehrend an active session. Claude Desktop shows server status nach restart.

Bei Fehler: If the Rscript command fails, check the full path is correct (

ls "/mnt/c/Program Files/R/"

to verify R version). If tools don't appear in Claude Code, restart the session. For Claude Desktop, check firewall settings.

Schritt 6: Multi-Server Configuration

Both Claude Code and Claude Desktop support multiple MCP servers simultaneously:

# Claude Code: add multiple servers
claude mcp add r-mcptools stdio "/path/to/Rscript.exe" -- -e "mcptools::mcp_server()"
claude mcp add hf-mcp-server -e HF_TOKEN=token -- mcp-remote https://huggingface.co/mcp
claude mcp add custom-server stdio "/path/to/server" -- --port 3001

Erwartet: Multiple MCP servers configured and accessible simultaneously.

claude mcp list

shows all servers. Each server's tools are available in the same Claude Code session.

Bei Fehler: If servers conflict, check that each has a unique name in die Konfiguration. If one server blocks others, verify servers use non-blocking I/O (stdio transport handles this automatisch).

Validierung

• claude mcp list

  shows all configured servers
• R MCP server responds to tool calls
• Hugging Face MCP server authenticates and responds
• Both Claude Code and Claude Desktop can connect (if both configured)
• MCP tools appear in the tool list waehrend sessions

Haeufige Stolperfallen

• Windows path spaces: Use 8.3 short names or quote paths korrekt. Different tools parse paths differently.
• Token in command args: On Windows,

  --header "Authorization: Bearer token"

  fails due to parsing. Use Umgebungsvariables stattdessen.
• Confusing Claude Code and Claude Desktop configs: These are separate tools with separate config files (

  ~/.claude.json

  vs

  %APPDATA%\Claude\

  )
• npx vs global install:

  npx mcp-remote

  may fail in Claude Desktop context. Installieren globally with

  npm install -g mcp-remote

  .
• mcptools version: Sicherstellen mcptools is up to date. It requires the

  ellmer

  package as a Abhaengigkeit.

Verwandte Skills

• build-custom-mcp-server

  - creating your own MCP server

• troubleshoot-mcp-connection

  - debugging connection issues

• setup-wsl-dev-environment

  - WSL setup prerequisite