three.ws 3D Agent Tools MCP Server

What the code does

We read the source, 1 min ago · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

        'http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token',

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

        const r = await redis.eval(

        const proc = spawn(ffmpegPath(), ['-hide_banner', '-loglevel', 'error', '-i', 'pipe:0', ...args, 'pipe:1']);

    const [row] = await sql`SELECT voice_provider, voice_id FROM agent_identities WHERE id = ${agentId}`.catch(() => []);

                return JSON.parse(await readFile(path.join(base, rel), 'utf8'));

    return subprocess.run(

        exec(compile(job["code"], "<three-ws-blender-mcp>", "exec"), namespace)

            if (reset) { state.cursor = null; state.total = 0; grid.innerHTML = skeletons(); stateEl.hidden = true; }

        `https://api.telegram.org/bot${cfg.token}/sendMessage`,

    "bytecode": "0x60806040523480156200001157600080fd5b5060405162000dd238038062000dd2833981016040819052620000349162000351565b8383600362000044838262000477565b50600462000053828262000477565b5050506001600160a01b038116620000a65760405162461bcd60e51b8152602060048201526011602482015270726…

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add 3d-agent-mcp -- npx -y @three-ws/mcp-server

{
  "mcpServers": {
    "3d-agent-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/mcp-server"
      ]
    }
  }
}

[mcp_servers.3d-agent-mcp]
command = "npx"
args = ["-y", "@three-ws/mcp-server"]

{
  "mcpServers": {
    "3d-agent-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/mcp-server"
      ]
    }
  }
}

{
  "servers": {
    "3d-agent-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/mcp-server"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: MCP_SVM_PAYMENT_ADDRESS (Solana address that receives USDC when a client pays for a tool call (falls back to X402_PAY_TO_SOLANA / X402_PAY_TO). Required to settle paid tools), SOLANA_RPC_URL (Solana mainnet RPC endpoint. Defaults to the public cluster — bring your own (Helius / Quicknode / Triton) for production traffic), HELIUS_API_KEY (Optional Helius API key — enables exact supply and richer DAS data in pump.fun snapshots).