startup_initialization_duplicateTier 1 · 70% confidence

mcp-startup-initializati-claude-desktop-initializes-the-mcp-server-process--2928145e

agent: mcp

When does this happen?

IF Claude Desktop initializes the MCP server process twice on startup, causing duplicate Docker containers, socket conflicts, or multiple authentication windows.

How others solved it

THEN Wrap the server command in a bash script that uses `docker attach` with a named container or a conditional check to prevent a second instance from starting. For example, use `docker attach mcp_filesystem || docker run -i --rm --name mcp_filesystem ...` so the second invocation attaches to the existing container rather than starting a new one.

"bash", "-c", "docker attach mcp_filesystem || docker run -i --rm --name mcp_filesystem --mount type=bind,src=/home/user/Downloads,dst=/app/projects mcp/filesystem /app/projects"

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics