-
Notifications
You must be signed in to change notification settings - Fork 0
IDE Configuration
The mcpServers JSON block itself is the same everywhere (see README.md
for the full example). What differs per IDE is where that JSON goes.
Project-scoped config lives in .mcp.json at your repo root, or use the
CLI:
claude mcp add modhelper-mcp -- python -m modhelper_mcp.serverThen set env vars either in that same command (--env KEY=value) or by
editing .mcp.json directly to add the env block from README.md's
example. Restart Claude Code after editing .mcp.json for changes to take
effect.
~/.cursor/mcp.json for a config that applies everywhere, or
.cursor/mcp.json inside a specific project for a project-scoped one.
Paste the exact JSON block from README.md Option A or B. Cursor picks up
changes on restart, not live.
Open the Customizations panel (... dropdown in the agent panel) →
MCP settings. The exact settings file location varies by Antigravity
version - check its own MCP panel for the path, then paste the same JSON
block. Antigravity shows enabled tools directly in its UI as a toggle
list per server, which is a useful way to confirm your
MODHELPER_MCP_ENABLED_TOOLS value actually took effect (only tools from
enabled groups will appear there).
~/.codeium/windsurf/mcp_config.json. Same JSON shape, key name is
serverUrl for remote servers but command/args/env for local ones
like this MCP - use the command form from README.md.
-
Don't use the
.shfiles underscripts/orbin/from PowerShell -chmodand shell scripts don't exist there. Always use thepython -m modhelper_mcp.serverform (Option B inREADME.md), withcwdpointing at this folder. - If your IDE's config format doesn't support a
cwdfield, setPYTHONPATHinsideenvinstead, pointing at this folder's absolute path. - Windows paths in JSON need doubled backslashes:
"C:\\Users\\You\\...\\modhelper_mcp", not single ones.
After restarting your IDE, ask your agent something that must come from this MCP, not general knowledge - e.g. "search modrinth for Create mod" - rather than just checking the tool list is present. A tool showing up in the list only confirms the server started; it doesn't confirm your API keys or enabled-groups value are actually correct.
ModHelper-MCP