systemd and cli use differnt config files

[tomdavidson]

Hello, just upgraded and thank you for this awesome software.

I disabled and removed the manually installed bin and systemd service and then installed via apt.

The systemd services uses -config=/etc/mcpproxy/mcp_config.json --data-dir=/var/lib/mcpprox but the cli reports Config: /home/{user}/.mcpproxy/mcp_config.json

Did I mess something up on the install? do they use different configs intentionally, how do I use the cli with the systemd instance?

[itzmitto]

The different paths match the documented package layout. The apt package runs as the dedicated mcpproxy user, with configuration in /etc/mcpproxy/ and state in /var/lib/mcpproxy/. A normal CLI invocation uses your own user’s defaults.

See the installation and migration documentation and the packaged systemd unit.

With the service running, check that its default socket exists:

sudo ls -l /var/lib/mcpproxy/mcpproxy.sock

If it exists, try listing the service’s upstream servers explicitly:

sudo -u mcpproxy env \
  MCPPROXY_TRAY_ENDPOINT=unix:///var/lib/mcpproxy/mcpproxy.sock \
  /usr/bin/mcpproxy upstream list \
  --config=/etc/mcpproxy/mcp_config.json \
  --data-dir=/var/lib/mcpproxy

This selects the packaged binary, service configuration and daemon socket. Running as mcpproxy respects the socket’s owner-only permissions.

The CLI client-mode documentation describes the endpoint override. Simply pointing --config at the service’s file is different from connecting to its running daemon.

If the socket is missing or this returns an error, which MCPProxy version are you running, and what is the exact error?

[tomdavidson]

The CLI would recreate ~/.mcpproxy/mcp_config.json so there was confusion of which config was being used. The solution for me was to just make my own systemd services in user space.

v0.7.1

Thanks again.