Does mcp_service run under run_local, or is MCP local-workspace access not yet supported for self-hosted?

[dblanchard]

I## Summary
I'm trying to set up Macro to run fully locally with inferrence served by Ollama.

mcp_service and mcp_auth_proxy exist as full services in the repo, and
infra/stacks/mcp-server/ has its own Pulumi stack, but neither service
appears in docker/docker-compose.yml or has a justfile recipe. Is MCP
access to a local workspace supported under run_local/stack, or is
mcp_service intended only for the hosted AWS deployment right now?

What I've checked

• grep -rn "mcp_service\|mcp_auth_proxy" docker/docker-compose.yml — no matches
• grep -n "mcp" justfile — no matches
• curl http://localhost:<proxy-port>/mcp against a running local stack returns
  Caddy's generic fallback response, not an actual MCP endpoint
• cargo run -p mcp_service compiles but fails immediately on
  Connection refused (os error 111) from sqlx — no DATABASE_URL (or
  equivalent) is set when running the service outside run_local's env
  injection

Environment

• Self-hosting via just run_local --no-doppler --instance <name> --port-base <n>
• WSL2 (Ubuntu), Docker Compose v5.1.1, Nix devShell
• Goal: connect an external MCP client (Hermes Agent / Open Interpreter) to
  the local workspace's memory/docs

Question

Is there a documented way to run mcp_service against a local run_local/
stack instance? If not yet supported, is that on the near-term roadmap, or
is the intended self-host path to point external MCP clients at the hosted
mcp-server.macro.com endpoint even when the workspace itself is
self-hosted?
EOF

[cameronapak]

Hey @dblanchard thanks for submitting this! Also wanted to share #5666 (comment)