Security notes

The MCP server is a thin proxy in front of the 0detect Local API. Whoever can invoke its tools can do everything your API key allows.

Use a dedicated API key for the MCP server when 0detect supports per-key separation, and follow the principle of least privilege.
The API key is read from ~/.0detect/config.json, which 0detect itself manages. Keep this file readable only by your user account, and never commit it to a repository.
If you suspect the key was exposed, rotate it inside 0detect and restart your MCP host so the server picks up the new value.
Only run the MCP server on machines that you trust to host your antidetect profiles.

Common issues

Symptom	What to check
Connection / `fetch` errors	Is 0detect actually running? Does `~/.0detect/config.json` exist with a valid `localApiPort`? Is the port blocked by a firewall or bind address?
`401` / authentication errors	Is `localApiKey` present and current in `~/.0detect/config.json`? After 0detect rotates the key, restart the MCP host so the new value is loaded.
MCP host shows no tools	Run `npm start` in a terminal and confirm the process starts without crashing. Check host logs for spawn errors and absolute path mistakes.
Garbled protocol output / unexpected disconnects	Don't pipe extra tools into the same stdout. The server already redirects `console.log` to stderr — do the same for any custom logging.
Tool calls succeed but `body` is empty or unexpected	Compare against the local `swagger.json` at `http://localhost:56789/swagger.json` — the upstream contract is authoritative.

Diagnostics

Quick checks to narrow the problem down:

# Is the local API alive?
curl -i http://localhost:56789/health-check
 
# Does the config file exist and have the expected fields?
cat ~/.0detect/config.json
 
# Does the MCP server start cleanly?
cd /absolute/path/to/0detect-mcp && npm start

If npm start exits immediately or prints an error to stderr, fix that first — the MCP host can't talk to a server that won't stay up.

Reporting issues

Bugs and feature requests for the MCP server go to the github.com/0detect/mcp-server (opens in a new tab) issue tracker. Include:

Your Node.js version (node --version).
The MCP host name and version (e.g. Cursor 0.x, Claude Desktop x.y).
The exact tool call and the full JSON response (without your API key).

Tools reference FAQ