Claude apps

The two Claude apps take Wellworn by different routes. On claude.ai a remote MCP server is a custom connector, added by URL from the settings UI. Claude Desktop has no UI for remote servers: its claude_desktop_config.json starts local programs, so a remote endpoint reaches it through a stdio bridge.

claude.ai, without a key

On Pro and Max, open Customize, then Connectors, then +, then Add custom connector, and paste:

https://mcp.wellworn.dev/mcp

On Team and Enterprise an owner adds it once for the organization under Organization settings, then Connectors, then Add, then Custom, then Web. Free accounts can hold one connector.

The Advanced settings panel on that dialog takes an OAuth Client ID and Client Secret. Wellworn has no OAuth server, so leave both empty and the connector runs on the no-key tier at 60 calls a day.

Verified 2026-09-08 against support.claude.com

Claude Desktop, without a key

Open the Claude menu, Settings, the Developer tab, then Edit Config. That writes ~/Library/Application Support/Claude/claude_desktop_config.json on macOS and %APPDATA%\Claude\claude_desktop_config.json on Windows.

{
  "mcpServers": {
    "wellworn": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.wellworn.dev/mcp"]
    }
  }
}

Node.js has to be installed for npx to resolve.

Claude Desktop, with a key

mcp-remote has a documented spacing bug with Claude Desktop on Windows, so put the whole header value in an environment variable and write the flag without a space after the colon.

{
  "mcpServers": {
    "wellworn": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.wellworn.dev/mcp",
        "--header",
        "Authorization:${WELLWORN_AUTH}"
      ],
      "env": {
        "WELLWORN_AUTH": "Bearer ww_your_key"
      }
    }
  }
}

Confirm it works

Quit Claude Desktop completely and start it again; it loads the config only at launch. Then click Add files, connectors, and more at the bottom left of the input box, hover Connectors, click Manage connectors, and select Wellworn to see its eight tools.

What breaks

A relative path or a missing npx shows up in the logs rather than the UI. They are at ~/Library/Logs/Claude on macOS and %APPDATA%\Claude\logs on Windows; mcp.log holds connection failures and mcp-server-wellworn.log holds the bridge's own stderr.

tail -n 20 -f ~/Library/Logs/Claude/mcp*.log

Verified 2026-09-08 against modelcontextprotocol.io