Currently, the configuration executes load_dotenv() in config.py:4 without specifying an absolute file path.
The Issue:
If an MCP client (such as Claude Desktop) launches the server from a different working directory, load_dotenv() fails to locate the local .env file. The server fails to load the RAINDROP_ACCESS_TOKEN and will crash when an LLM attempts to execute a tool.
Potential Interventions:
- Hardcode the Relative Path: Modify
config.py to resolve the .env file explicitly relative to the __file__ constant.
- Architectural Standardisation: Abandon the
.env file for production usage. Mandate in the documentation that users inject the token directly via their MCP client's configuration file (e.g., claude_desktop_config.json).
Currently, the configuration executes
load_dotenv()inconfig.py:4without specifying an absolute file path.The Issue:
If an MCP client (such as Claude Desktop) launches the server from a different working directory,
load_dotenv()fails to locate the local.envfile. The server fails to load theRAINDROP_ACCESS_TOKENand will crash when an LLM attempts to execute a tool.Potential Interventions:
config.pyto resolve the.envfile explicitly relative to the__file__constant..envfile for production usage. Mandate in the documentation that users inject the token directly via their MCP client's configuration file (e.g.,claude_desktop_config.json).