Documentation: Using npx/uvx is discouraged, better use containers?

[amotl]

Just sharing an excerpt from the backlog, about getting rid of uvx?

cratedb-mcp/docs/backlog.md

Lines 14 to 16 in 89a4dc0

	- Install: Others also just use `docker` right away? Others discourage using `uvx`.
	- https://github.com/ppl-ai/modelcontextprotocol/?tab=readme-ov-file#step-3-configure-claude-desktop
	- https://medium.com/@scalablecto/stop-running-your-mcp-tools-via-npx-uvx-right-now-380d1ab99d3f

Originally posted by @amotl in #23 (comment)

@kneth says:

Looks like consensus hasn't been reach yet. Let's return to it once it has.

[amotl]

@WalBeh also prefers to use uv tool install.

[amotl]

Shipping per OCI seems to be advertised as well.

• Provide OCI image(s) #45

[...] at least by Docker:

[...] No more hardcoded secrets, no more launching tools with full host access via npx or uvx, and no more compromising on isolation or security. [...]

• https://www.docker.com/blog/introducing-docker-mcp-catalog-and-toolkit/
• https://www.docker.com/blog/introducing-docker-hub-mcp-server/
• https://docs.docker.com/ai/mcp-catalog-and-toolkit/toolkit/
• https://github.com/docker/mcp-registry/blob/main/CONTRIBUTING.md
• https://docs.docker.com/ai/mcp-catalog-and-toolkit/toolkit/#example-use-visual-studio-code-as-a-client

[amotl]

Shipping per OCI seems to be advertised as well: No more compromising on isolation or security.

The project will start providing OCI images to satisfy isolation needs.

• OCI: Add building OCI images cratedb-mcp and cratedb-mcpo #50