Publish Docker Image

[crepererum]

#5 added a Dockerfile specifically for Smithery. It would be nice if that image could be also be published to some registry (GitHub oder docker.io or something), so people can use the MCP server locally w/o requiring node.js on the host (it's also better for security isolation).

[crepererum]

A somewhat slow workaround is to use the node image with npx:

docker run -e DEEPL_API_KEY --rm -i node npx --yes deepl-mcp-server

[morsssss]

Hi @crepererum !

We get the advantages of hosting our own Dockerfile that you mention... but we're still not sure it's worth doing. I'd like to make the MCP easier for nonprogrammers to install, but if they can't use node, they probably can't use docker either :) And the server is so simple right now that we're not sure there are strong security reasons to run it in a container.

On the other hand, we do want to publish a remote server too as per #28 .

Let us know if you want to contribute this though!

[crepererum]

The reasons why I would prefer to run the server within a container are:

• you don't need to pollute the host system with node (probably even with multiple versions of nodes if you have other servers that need other major node releases)
• you greatly reduce the attack surface and review time for the different MCP servers. Running arbitrary code unsandboxed isn't exactly best practice. No offense, I'm sure you do your best to provide a secure implementation, but you have to consider this on a grant scale of people/deployments with a larger number of MCP servers.