<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><title>Plugolis: MCP fixes and guides</title><link>https://plugolis.com/</link><description>The MCP server directory and fix guide</description><lastBuildDate>Thu, 15 Oct 2026 14:34:37 GMT</lastBuildDate>
<item><title>Where to host a remote MCP server</title><link>https://plugolis.com/guides/host-remote-mcp-server/</link><guid>https://plugolis.com/guides/host-remote-mcp-server/</guid><description>When you need a remote (HTTP) MCP server instead of a local one, what a host must support, and the main options.</description></item>
<item><title>MCP server not showing in Cursor (or showing a red dot)</title><link>https://plugolis.com/fixes/mcp-server-not-showing-in-cursor/</link><guid>https://plugolis.com/fixes/mcp-server-not-showing-in-cursor/</guid><description>Cursor only reads ~/.cursor/mcp.json (global) or .cursor/mcp.json in the project root. A wrong file location, a typo in the mcpServers key, invalid JSON, or a command that crashes on start all leave the server missing or red.</description></item>
<item><title>MCP server not showing in Claude Desktop</title><link>https://plugolis.com/fixes/mcp-server-not-showing-in-claude-desktop/</link><guid>https://plugolis.com/fixes/mcp-server-not-showing-in-claude-desktop/</guid><description>Claude Desktop reads claude_desktop_config.json only at startup. Editing the wrong file, invalid JSON, or not fully quitting the app (it keeps running in the tray/menu bar) are the usual causes.</description></item>
<item><title>Fix &quot;spawn npx ENOENT&quot; when starting an MCP server</title><link>https://plugolis.com/fixes/spawn-npx-enoent/</link><guid>https://plugolis.com/fixes/spawn-npx-enoent/</guid><description>The app launched the server without your shell's PATH, so it cannot find npx. This is common with nvm, fnm, Volta, or Homebrew installs, because GUI apps do not load ~/.zshrc / ~/.bashrc.</description></item>
<item><title>MCP servers fail on Windows with npx (use cmd /c)</title><link>https://plugolis.com/fixes/windows-npx-mcp-cmd-c/</link><guid>https://plugolis.com/fixes/windows-npx-mcp-cmd-c/</guid><description>On Windows, npx is a npx.cmd batch script, which cannot be spawned directly without a shell. Clients that spawn the command directly fail.</description></item>
<item><title>MCP server can't see my API key (env vars not passed)</title><link>https://plugolis.com/fixes/mcp-env-vars-not-passed/</link><guid>https://plugolis.com/fixes/mcp-env-vars-not-passed/</guid><description>MCP clients start servers with a minimal environment. Variables exported in your shell profile are usually not inherited, so the key has to be put in the server's env block (or passed with the client's CLI flag).</description></item>
<item><title>MCP config JSON syntax errors (trailing commas, comments, quotes)</title><link>https://plugolis.com/fixes/mcp-json-config-syntax-error/</link><guid>https://plugolis.com/fixes/mcp-json-config-syntax-error/</guid><description>MCP config files are strict JSON: no trailing commas, no comments, double quotes only, and backslashes must be escaped. One error disables every server in the file.</description></item>
<item><title>Too many MCP tools: tool limits in Windsurf, Cursor and VS Code</title><link>https://plugolis.com/fixes/cursor-too-many-mcp-tools/</link><guid>https://plugolis.com/fixes/cursor-too-many-mcp-tools/</guid><description>Agents work best with a limited set of tools, and some clients enforce a hard cap. Windsurf's docs say Cascade has a limit of 100 total tools at any given time. Cursor's and VS Code's current MCP docs don't publish a fixed number, but both let you switch tools off. Big servers like GitHub or AWS can</description></item>
<item><title>Fix &quot;spawn uvx ENOENT&quot; for Python MCP servers</title><link>https://plugolis.com/fixes/spawn-uvx-enoent/</link><guid>https://plugolis.com/fixes/spawn-uvx-enoent/</guid><description>Python servers such as fetch, git, time, and many awslabs servers launch with uvx, which comes from uv. Either uv isn't installed, or it lives in ~/.local/bin, which GUI apps don't have on their PATH.</description></item>
<item><title>&quot;MCP error -32000: Connection closed&quot;: what it means and how to fix it</title><link>https://plugolis.com/fixes/mcp-error-32000-connection-closed/</link><guid>https://plugolis.com/fixes/mcp-error-32000-connection-closed/</guid><description>The server process exited before it finished the handshake. Common reasons: a missing dependency, wrong Node version, missing API key, bad args, or Windows npx without cmd /c. The real error is in the server's stderr.</description></item>
<item><title>&quot;MCP error -32001: Request timed out&quot;</title><link>https://plugolis.com/fixes/mcp-error-32001-request-timed-out/</link><guid>https://plugolis.com/fixes/mcp-error-32001-request-timed-out/</guid><description>The client gave up waiting. On first run, npx/uvx may still be downloading the package. Slow tools (browser automation, big crawls) can also go over the default timeout.</description></item>
<item><title>&quot;Unexpected token … is not valid JSON&quot; from a custom MCP server</title><link>https://plugolis.com/fixes/mcp-stdout-not-valid-json/</link><guid>https://plugolis.com/fixes/mcp-stdout-not-valid-json/</guid><description>With the stdio transport, stdout is reserved for JSON-RPC messages. Any console.log / print() to stdout corrupts the stream.</description></item>
<item><title>MCP server crashes because the client uses an old Node version</title><link>https://plugolis.com/fixes/mcp-server-wrong-node-version/</link><guid>https://plugolis.com/fixes/mcp-server-wrong-node-version/</guid><description>With nvm installed, a GUI app may pick up an old system Node (e.g. v16) instead of your nvm default. Modern MCP servers need Node 18+ and often 20+.</description></item>
<item><title>Claude Code: MCP server added but not available (&quot;No MCP servers configured&quot;)</title><link>https://plugolis.com/fixes/claude-code-mcp-server-not-found/</link><guid>https://plugolis.com/fixes/claude-code-mcp-server-not-found/</guid><description>claude mcp add defaults to local scope, which only applies to the current project directory. Open a different folder and the server is gone.</description></item>
<item><title>VS Code ignores my MCP config (&quot;servers&quot; vs &quot;mcpServers&quot;)</title><link>https://plugolis.com/fixes/vscode-mcp-servers-key/</link><guid>https://plugolis.com/fixes/vscode-mcp-servers-key/</guid><description>VS Code's .vscode/mcp.json uses a top-level servers key, not mcpServers like Cursor and Claude Desktop.</description></item>
<item><title>GitHub MCP server: &quot;Bad credentials&quot; / 401 errors</title><link>https://plugolis.com/fixes/github-mcp-bad-credentials/</link><guid>https://plugolis.com/fixes/github-mcp-bad-credentials/</guid><description>The token is missing, expired, or lacks scopes. With Docker, the variable also has to be forwarded into the container (-e GITHUB_PERSONAL_ACCESS_TOKEN) and set in the env block.</description></item>
<item><title>Windsurf: MCP server not loading in Cascade (mcp_config.json location)</title><link>https://plugolis.com/fixes/windsurf-mcp-config-not-loading/</link><guid>https://plugolis.com/fixes/windsurf-mcp-config-not-loading/</guid><description>Windsurf's current docs put mcp_config.json at ~/.config/devin/mcp_config.json (macOS/Linux) or %APPDATA%\devin\mcp_config.json (Windows). Older guides point at ~/.codeium/windsurf/. The file applies only to the legacy Cascade agent; the default Devin Local agent reads the Devin CLI config instead. </description></item>
</channel></rss>
