What dependencies are needed for the Jetbrains configuration?
Node.js and `npx` must be installed on Windows, and the MCP Server plugin must be enabled in the Jetbrains IDE. External connections must be allowed in the IDE’s debugger settings.
@bcdennis
Basic information
This is a reference implementation of the mcp config to show different use cases for how to configure MCP servers with an app that hosts an MCP Client (like Claude Desktop)
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
This resource provides reference JSON configurations for connecting Claude Desktop to MCP servers across different environments, including Jetbrains IDEs on Windows, Docker containers on the Windows host or WSL, and uvx‑packaged servers in WSL. It is intended for Claude Desktop users who need practical, copy‑and‑paste setup examples for these common integration scenarios.
Copy the relevant JSON snippet into your Claude Desktop configuration file. For Jetbrains, first install the MCP Server plugin, enable external connections in the IDE, and ensure the port matches. For Docker or WSL setups, adjust paths, tokens, and mount points as shown. After adding the configuration, restart Claude Desktop to apply the changes.
npx on WindowsNode.js and `npx` must be installed on Windows, and the MCP Server plugin must be enabled in the Jetbrains IDE. External connections must be allowed in the IDE’s debugger settings.
Jetbrains changes the IDE port on every launch. Instead of updating the Claude config each time (which requires restarting the app), update the Jetbrains IDE port to match the port already set in your Claude configuration.
The `GITHUB_PERSONAL_ACCESS_TOKEN` environment variable must be set. In the provided Docker example, the token is passed via `-e` and referenced in the `env` block of the config.
Use `wsl.exe` as the command and pass the full `docker run` command as arguments. For example, the filesystem server uses a bind mount from the WSL filesystem into the container.
You need `uvx` and a shell inside WSL. The config uses `wsl.exe bash -c` to invoke `uvx` with the full path to the binary, along with the appropriate repository path for the git MCP server.

One case file per task — shared by every session, agent and person that touches it. Self-hosted MCP server and live board. MIT.

Local-first credential broker for MCP. AI coding agents (Claude Code, Cursor, Codex…) call APIs, SSH and databases through scoped presets; secrets stay in your OS keychain and never enter the agent's context.

The tools your AI needs to make your games. Turn prompts into production-ready game assets — animated characters with their weapons attached, seamless textures, terrain, VFX, HUDs — and playable game kits Unity, Godot, U
ZeroBeacon.ai — Collision-proof commerce router for AI agents. 1000 MCP tools: commerce, trust, billing, sovereign ID + everyday tools. LIVE.
OrangePro local-first CLI + MCP server for behavior mapping, grounded test generation, and dynamic proof.
Comments