autoresearchclaw-container-topology-oracle-network

The researchclaw container is deployed on oracle-network alongside the existing oracle-hermes, oracle-mirofish, and oracle-graphiti-mcp containers. AutoResearchClaw requires Docker-in-Docker or host Docker socket access for its own experiment sandbox containers (it executes generated code in isolated sub-containers). The MCP server runs inside the researchclaw container and is registered as a session-based MCP server (not permanent) to keep the tool budget lean. Authentication between oracle-hermes and researchclaw MCP uses a shared API token injected via environment variable.

Related

• docker
• researchclaw-dedicated-container-oracle-network-deployment
• autoresearchclaw-requires-dedicated-container-for-sandbox
• autoresearchclaw-requires-dedicated-container-for-experiment
• researchclaw-dedicated-container-required-for-sandbox
• researchclaw-container-requires-docker-socket-mount
• researchclaw-requires-dedicated-container-with-docker-socket
• researchclaw-dedicated-container-isolation-requirement
• oracle-network-container-topology-pattern