the MCP server is a child process of whatever process you started, it inherits your UID, and ~/.ssh is readable by you. I didn't need to expressly give it anything, it had it from the time it was activated, that's kind of the point

I think we are in agreement with your statement, up until the second part of it.

Like i said, its a best practice to run MCP servers, etc with their own user account and access and not with your own account.

The moment you ran your app with your own credentials you exactly granted it permission to everything you can access include ~/.ssh