# Troubleshooting

> The HeyLead setups that fail most and what to do: missing claude or uvx, 401 needs authentication, no tools after adding, conflicting server entries, LinkedIn not connected, sign-in and network failures.

This is the Markdown twin of https://heylead.dev/docs/troubleshooting (the page, in text). Index for agents: https://heylead.dev/llms.txt

## `claude` or `uvx` is missing

Use the hosted path for your client in the [quickstart](https://heylead.dev/docs/quickstart). Neither is needed for a desktop custom connector or for Cursor and VS Code, which take the remote URL.

## 401, needs authentication

Authenticate from the client's MCP panel; the browser sign-in is the fix. Discovery is at `/.well-known/oauth-protected-resource` and `/.well-known/oauth-authorization-server`. Retrying tool calls without signing in changes nothing.

## No tools after adding the server

Check the client and the scope the entry landed in, reconnect or start a new session, then verify with `show_status`. A restart has not happened until you restarted.

## Two entries for heylead

A local stdio entry named `heylead` and a remote HTTP entry can coexist in different scopes, and the client loads one of them. Keep the remote entry for a hosted account, keep the stdio entry for a self-hosted install, and do not put an HTTP entry in `claude_desktop_config.json`, which is stdio only.

## MCP is connected but LinkedIn is not

They are two different connections. Connect LinkedIn in the [dashboard](https://heylead.dev/dashboard/), then call the read-only `accounts` tool. An empty workspace is valid.

## Sign-in or network failure

Read the actual error the client shows and act on it. Do not report setup success on a guess, and do not fall back to a guessed package name.

## Something else

Write to [hello@heylead.dev](mailto:hello@heylead.dev) or open an issue on [GitHub](https://github.com/D4umak/linkedin-outreach-mcp/issues). For security, see [security.txt](https://heylead.dev/.well-known/security.txt).