-
Notifications
You must be signed in to change notification settings - Fork 352
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
What version of eigent are you using?
0.0.60
System information
Environment Details
- Platform: macOS (darwin 24.5.0)
- Eigent Version: Latest (as of September 1, 2025)
- WhatsApp Bridge: Running locally on port 8080
- MCP Configuration: Present in both Cursor and Eigent configs
Problem description
WhatsApp MCP integration works perfectly in Cursor but fails in Eigent due to worker node environment isolation.
Issue Description
Expected Behavior
Eigent should be able to use WhatsApp MCP tools (send messages, list contacts, etc.) just like Cursor does.
Actual Behavior
Eigent worker nodes report: "I cannot proceed because direct programmatic access to WhatsApp via an official 'whatsapp mcp' is not available on this system."
Steps to Reproduce
- Configure WhatsApp MCP in Eigent's config file (
~/.eigent/mcp.json) - Start WhatsApp bridge locally (
go run main.goin whatsapp-bridge directory) - Try to send WhatsApp message via Eigent
- Observe error from worker node
Technical Details
Working Configuration (Cursor)
{
"mcpServers": {
"whatsapp": {
"command": "/Users/sarthak/.local/bin/uv",
"args": [
"--directory",
"/Users/sarthak/whatsapp mcp/whatsapp-mcp/whatsapp-mcp-server",
"run",
"main.py"
]
}
}
}Identical Configuration (Eigent)
{
"mcpServers": {
"whatsapp": {
"command": "/Users/sarthak/.local/bin/uv",
"args": [
"--directory",
"/Users/sarthak/whatsapp mcp/whatsapp-mcp/whatsapp-mcp-server",
"run",
"main.py"
]
}
}
}Error Log
[error] BACKEND: ======
[32mResponse from Worker node 3fbb82e4-3513-40d6-93ca-e4822c7fd81f (Developer Agent: A master-level coding assistant with a powerful terminal. It can write and execute code, manage files, automate desktop tasks, and deploy web applications to solve complex technical challenges.):[39m
[31mI cannot proceed because direct programmatic access to WhatsApp via an official "whatsapp mcp" (multi-channel platform API) is not available on this system. WhatsApp currently restricts automated group messaging for consumer accounts and does not provide an official public command-line tool or MCP for group messaging without explicit user permission or credentials.
If you have access to any specific WhatsApp automation tool, library, or MCP API credentials, please provide details or usage instructions, and I will continue accordingly. Otherwise, this task cannot be completed as described.[31m
======
2025-09-01 14:28:52,703 - camel.camel.societies.workforce.workforce - ERROR - Task 1756716825621-6510.2 failed (attempt 1/3): I cannot proceed because direct programmatic access to WhatsApp via an official "whatsapp mcp" (multi-channel platform API) is not available on this system. WhatsApp currently restricts automated group messaging for consumer accounts and does not provide an official public command-line tool or MCP for group messaging without explicit user permission or credentials.
If you have access to any specific WhatsApp automation tool, library, or MCP API credentials, please provide details or usage instructions, and I will continue accordingly. Otherwise, this task cannot be completed as described. (assigned to worker: 3fbb82e4-3513-40d6-93ca-e4822c7fd81f)
[info] BACKEND: 2025-09-01 14:29:00.345 | INFO | app.utils.toolkit.human_toolkit:ask_human_via_gui:46 - Question: To proceed with sending WhatsApp group messages, do you have access to any WhatsApp automation tool, official WhatsApp API, MCP credentials, or a bot that can send group messages? If yes, please provide the required integration details or credentials. If not, I can offer to send the message to the group using another messaging platform such as email or Slack. Please advise how you would like to proceed.
[info] BACKEND: 2025-09-01 14:29:30.870 | INFO | app.utils.toolkit.human_toolkit:ask_human_via_gui:59 - User reply: yes we have added the MCP credentials for whatsapp
[info] BACKEND: [33mWorker node 3fbb82e4-3513-40d6-93ca-e4822c7fd81f (Developer Agent: A master-level coding assistant with a powerful terminal. It can write and execute code, manage files, automate desktop tasks, and deploy web applications to solve complex technical challenges.) get task 1756716825621-6510.2: If the user has access to any WhatsApp automation tool, official API, MCP credentials, or a bot that can send group messages, prompt them to provide the required integration details or credentials. Otherwise, offer to send the same message to the group using another supported messaging platform such as email or Slack, and confirm the action to the user.[39m
INFO: 127.0.0.1:65096 - "POST /chat/1756716825621-6510/human-reply HTTP/1.1" 201 Created
[info] BACKEND: ======
[32mResponse from Worker node 3fbb82e4-3513-40d6-93ca-e4822c7fd81f (Developer Agent: A master-level coding assistant with a powerful terminal. It can write and execute code, manage files, automate desktop tasks, and deploy web applications to solve complex technical challenges.):[39m
[32mThank you for confirming that MCP credentials for WhatsApp have been added. Please provide the specified message that you want to send to a WhatsApp group and, if possible, indicate the target group from your group list. Once you provide this information, I will proceed to send the message to the selected WhatsApp group and confirm the action.[32m
======
[36m🎯 Task 1756716825621-6510.2 completed successfully.[36m
INFO: 127.0.0.1:65531 - "PUT /task/1756716825621-6510/take-control HTTP/1.1" 204 No Content
[info] Starting new task
[info] Starting new task
Root Cause Analysis
Primary Issue
Eigent's worker nodes run in isolated environments and cannot access:
- Local MCP servers running on the user's machine
- Local file system paths
- Local network services (like the WhatsApp bridge on port 8080)
Secondary Issues
- Environment Isolation: Worker nodes don't have access to local development environment
- Path Resolution: Absolute paths in MCP config may not resolve in worker environment
- Network Access: Worker nodes can't reach localhost services
Critical Evidence from Extended Logs
The extended error logs reveal several important issues:
- Worker Node Confusion: The worker node initially claims WhatsApp MCP is not available, but then asks for "MCP credentials" after the user confirms they exist
- Inconsistent State: The worker node says "Thank you for confirming that MCP credentials for WhatsApp have been added" but still cannot access the MCP server
- Task Completion Misleading: The task shows as "completed successfully" even though no WhatsApp message was actually sent
- Human Intervention Required: The system falls back to asking the user via GUI instead of using the configured MCP server
This demonstrates that:
- The MCP configuration is being read (worker knows about WhatsApp MCP)
- But the worker cannot actually connect to the local MCP server
- The system provides misleading success indicators
- The fallback mechanism doesn't solve the core issue
Verification Steps
✅ What Works
- WhatsApp MCP in Cursor (same configuration)
- WhatsApp bridge running locally on port 8080
- Direct REST API calls to localhost:8080
- MCP configuration syntax is correct
❌ What Doesn't Work
- Eigent worker nodes accessing local MCP server
- Path resolution in worker environment
- Network access to localhost services
Impact
- Users cannot use WhatsApp integration in Eigent
- MCP configuration appears correct but is not functional
- Creates confusion about whether configuration is valid
Files Involved
~/.eigent/mcp.json- Eigent MCP configuration (I have added via the UI)/Users/sarthak/whatsapp mcp/whatsapp-mcp/whatsapp-bridge/main.go- WhatsApp bridge/Users/sarthak/whatsapp mcp/whatsapp-mcp/whatsapp-mcp-server/main.py- MCP server
log
whatsapp second.log
whatsapplog.log
Additional context
No response
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working