DaemonsMCP

DaemonsMCP is a comprehensive MCP service written in C# that gives LLMs secure, full-featured access to explore, read, and modify your local codebases. It uses PackedTables.NET for fast, binary storage of configurations and supports features like code intelligence, multi-project management, and hot-reload file watching. You can navigate projects, read files, create/update/delete files and directories, back up destructive operations, and manage permissions. The DaemonsConfigViewer GUI provides an easy way to configure and manage all settings, projects, and security rules with live validation and hot-reload awareness. After starting the server, Claude or any compatible MCP client can issue RPC calls to browse the repository tree, read file contents, and perform write operations with safeguards and backups.

Prerequisites:

• .NET 9.0 SDK installed
• Build environment (e.g., Windows, Linux, or macOS with .NET tooling)
• Optional: Claude Desktop for integrated workflow

Step 1: Clone the repository

git clone https://github.com/mmeents/DaemonsMCP.git
cd DaemonsMCP

Step 2: Build the release version

# Build the release configuration
dotnet build --configuration Release

Step 3: Run the server

• On Windows, after a successful build, run the executable directly:

# From repository root, or use the published path
DaemonsMCP/bin/Release/net9.0/DaemonsMCP.exe

• Or use the dotnet command (preferred if you work with DLLs and cross-platform):

dotnet DaemonsMCP/bin/Release/net9.0/DaemonsMCP.dll

Step 4: Optional GUI configuration

• Run the DaemonsConfigViewer to configure projects and security settings via GUI:

cd DaemonsConfigViewer
dotnet run

Step 5: Verify configuration storage

• The server uses centralized storage under ProgramData on Windows or ~/.local/share on Linux/macOS. Ensure the paths exist or override with environment variables as needed.

Tips and common considerations:

• Centralized storage: DaemonsMCP moves configuration to a centralized location (e.g., C:\ProgramData\DaemonsMCP on Windows or ~/.local/share/DaemonsMCP on Linux/macOS). Ensure the process has write access to this directory.
• Security: The service includes multi-layer validation and backups. Use DaemonsConfigViewer to set per-project permissions and ensure only trusted LLMs can perform write operations.
• Backups: Writable destructive operations automatically create timestamped backups. Consider scheduling periodic backups for long-running projects.
• Hot reload: The RepositoryFileWatcher monitors changes and triggers reloads without restarting the service. Be aware of external edits from Claude/ConfigViewer and rely on the GUI indicators for changes.
• Data compatibility: If upgrading from older versions, migrate from per-project .daemons configurations to the centralized PackedTables storage as guided in the release notes.
• Environment variables: You can override default paths or enable integration with other tools by setting DAEMONSMCP_DATA_PATH and DAEMONSMCP_CONFIG_VIEWER_HOST as shown in the mcp_config env example.