Description
server/secops-soar/setup.py is out of sync with server/secops-soar/pyproject.toml and is missing the python-dotenv dependency.
Root Cause
PR #259 added "python-dotenv>=1.0.0" to server/secops-soar/pyproject.toml to support import dotenv in secops_soar_mcp.bindings.
However, server/secops-soar/setup.py (lines 24-27) was not synchronized:
setup(
name="secops-soar-mcp",
version="0.1.2",
packages=setuptools.find_packages(),
install_requires=[
"aiohttp>=3.11.15",
"mcp[cli]>=1.4.1,<2.0",
], # Missing python-dotenv>=1.0.0
...
)
Legacy packaging workflows, source distribution builds, or environments installing via setup.py will not pull in python-dotenv, leading to runtime ModuleNotFoundError: No module named 'dotenv' upon startup.
Proposed Fix
Synchronize server/secops-soar/setup.py by adding "python-dotenv>=1.0.0" to install_requires:
install_requires=[
"aiohttp>=3.11.15",
"mcp[cli]>=1.4.1,<2.0",
"python-dotenv>=1.0.0",
],
Description
server/secops-soar/setup.pyis out of sync withserver/secops-soar/pyproject.tomland is missing thepython-dotenvdependency.Root Cause
PR #259 added
"python-dotenv>=1.0.0"toserver/secops-soar/pyproject.tomlto supportimport dotenvinsecops_soar_mcp.bindings.However,
server/secops-soar/setup.py(lines 24-27) was not synchronized:Legacy packaging workflows, source distribution builds, or environments installing via
setup.pywill not pull inpython-dotenv, leading to runtimeModuleNotFoundError: No module named 'dotenv'upon startup.Proposed Fix
Synchronize
server/secops-soar/setup.pyby adding"python-dotenv>=1.0.0"toinstall_requires: