Wholix MCP
The Wholix MCP server exposes a curated set of tools that your AI assistant can call on your behalf. Every call runs as you against your Wholix account.
Server endpoint: https://dev.mcp.wholix.net/mcp
Server name (as clients see it): wholix-dev
See all 1 available tool →
Install
Claude Code (CLI)
claude mcp add wholix-dev https://dev.mcp.wholix.net/mcp --transport http --scope user \
&& claude mcp login wholix-dev
Chained login opens your browser to authorise. Once done, ask Claude anything about your Wholix data.
!
to run it in-session without opening a new terminal:
!claude mcp add wholix-dev .... After it completes, restart the session
(/exit then claude) so the new server is picked up.
Claude Desktop (Mac / Windows)
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"wholix-dev": {
"type": "http",
"url": "https://dev.mcp.wholix.net/mcp"
}
}
}
Restart Claude Desktop. Open the MCP panel, click wholix-dev to authorise.
Cursor
Edit ~/.cursor/mcp.json:
{
"mcpServers": {
"wholix-dev": {
"type": "http",
"url": "https://dev.mcp.wholix.net/mcp"
}
}
}
Restart Cursor. wholix-dev appears in Settings → MCP; click to authorise.
Windsurf
Edit ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"wholix-dev": {
"serverUrl": "https://dev.mcp.wholix.net/mcp"
}
}
}
Restart Windsurf. Approve the OAuth prompt when it opens.
ChatGPT (Web & Desktop)
Requires a paid tier: Plus, Pro, Business, Enterprise, or Edu (Free tier does not support custom MCP).
- Profile picture → Settings → Security and login (or Advanced)
- Enable Developer mode and accept the third-party warning
- Go to Connectors / Plugins → Add custom connector (OpenAI has renamed this section a couple of times in 2026 — the toggle is under Developer mode either way)
- Paste the server URL:
https://dev.mcp.wholix.net/mcp
ChatGPT completes OAuth in a browser tab and the tools appear in your chat automatically.
OpenAI Codex (CLI & Desktop)
Codex shares one config file (~/.codex/config.toml) across the CLI, IDE extension, and desktop app — one install covers all three.
codex mcp add wholix-dev --url https://dev.mcp.wholix.net/mcp \
&& codex mcp login wholix-dev
Verify with codex mcp list.
Any other MCP-capable client
Wholix MCP is spec-compliant (OAuth 2.1 + Dynamic Client Registration + Streamable HTTP). Any client that speaks these standards will work — no per-client integration on our side.
- Server URL:
https://dev.mcp.wholix.net/mcp - Server name to use:
wholix-dev - Transport: Streamable HTTP
- Auth: OAuth 2.1 (auto-discovers via
https://dev.mcp.wholix.net/.well-known/oauth-protected-resource)
If your client supports OAuth 2.1 with DCR, just point it at the URL — it'll register itself and prompt you to sign in.
If it needs a static bearer token, use the client's equivalent of claude mcp login to obtain one and paste it in the auth header.
Sample prompts to try
- "How many modules do I have enabled in Wholix?"
- "What Wholix modules can I use?"
- "Show me my Wholix user profile."
Troubleshooting
- "Needs authentication" doesn't go away — click the server in your client's MCP panel and choose authenticate, or run the client-specific auth command. Logins expire; if a token is old, re-authenticate.
- Tool call returns "No authenticated user found" — your access token doesn't map to a Wholix user. Remove the connector and re-install.
-
Connection refused — check the server URL matches your environment (local vs. production). This page reflects the URL of the server serving it:
https://dev.mcp.wholix.net/mcp.