Signal Messenger — eConnect AI Bot
The eConnect Signal Messenger Bot is a proprietary AI client built directly into Signal. Powered by xAI Grok, it lets you query your eConnect system in plain conversational language — right inside a direct message or group chat. No extra software to install.
This integration requires your eConnect server to be publicly accessible over the internet. Grok's MCP support makes API calls from xAI's servers directly to your eConnect server.
- ✅ Cloud-hosted eConnect — works out of the box
- ⚠️ On-premises deployments — requires port forwarding through your firewall to the eConnect service
- ❌ Closed/isolated networks — not supported without network access
Prerequisites
- An eConnect account with access to the data you want to query
- Access to the Signal Messenger app with the eConnect Bot available in your organization
- Your eConnect server must be reachable from the internet (cloud-hosted or with firewall port forwarding)
Step 1: Add the eConnect MCP Server
Inside Signal, open a direct message to the eConnect Bot, or use a group chat where the bot is a member. Then send a message asking it to add the MCP server:
@eConnect Bot Please add the eConnect MCP server https://mcp.econnect.ai/mcp
The bot will confirm the server has been added. You can manage your MCP servers at any time using natural language or the built-in slash commands:
| Command | Description |
|---|---|
/mcp add <name> <url> [auth] | Add or update an MCP server |
/mcp remove <name> | Remove an MCP server |
/mcp list | List all configured MCP servers |
/mcp notes <name> show|clear|modify | Manage operational notes for a server |
You can also just ask naturally: "Can you list my MCP servers?" or "Remove the eConnect server."
Step 2: Get Your Auth Token
The MCP server is now registered, but still requires authentication before it can access your data. Authentication uses an encrypted, reusable token — your actual username and password are never exposed to the AI.
- Navigate to https://mcp.econnect.ai/auth/
- Enter your eConnect server address — for example
portal.econnect.tv(the cloud entry point for most eConnect customers) - Enter your username and password
- Set the Token Validity — tokens expire after the duration you select:
- Default: 7 days (good for occasional use)
- Up to 30 days (if you use this frequently)
- Click Generate Token
Your credentials are encrypted with AES-256-GCM inside the token. The eConnect MCP server handles decryption on the backend — your username and password are never passed through the AI model or stored by mcp.econnect.ai.
Using a Dedicated User Account (Recommended)
Instead of using your personal credentials, consider creating a dedicated eConnect user for AI access:
- Create a new user account in eConnect with only the permissions the AI should have
- Restrict access using logical groups, tags, revenue centers, or plugins as needed
- Use that account's credentials when generating the token
- If the token is ever compromised, simply disable or delete that user
Step 3: Authenticate the Bot
Once you have your token, click "Copy with Prompt" on the auth page. This copies a ready-to-paste message with the token already embedded.
Paste it into your Signal chat with the eConnect Bot:
Can you login to eConnect and give me the plugins. Use this Token <your-token-here>
The bot will connect to your eConnect server and confirm the connection by listing your available plugins. From that point on, the token is remembered for the session — you only need to provide it again when it expires.
Step 4: Start Querying
Once authenticated, ask anything in natural language:
"Who was detected at the main entrance in the last hour?"
"Show me any POS exceptions from today."
"Give me a summary of face detections for the past week."
"What LPR events happened after midnight?"
What the Bot Can Do
Beyond querying eConnect data, the AI-powered bot can also:
- Generate images for presentations or reports
- Research anything with real-time web access (powered by Grok)
- Create face templates just by describing what you want
- Analyze trends and provide written summaries or insights
- Answer security questions about your facility using live data
Troubleshooting
| Problem | Solution |
|---|---|
| Bot can't reach your server | Verify your eConnect server is publicly accessible. Try accessing it from a browser outside your network. For on-premises, confirm port forwarding is configured correctly. |
| Token expired | Re-visit mcp.econnect.ai/auth/, generate a new token, and paste it into chat. Consider setting a longer validity period. |
| Bot says "no permission" | The user account used for the token may lack access to the requested module. Check permissions in eConnect and adjust the user's role or group membership. |
| MCP server not listed | Use /mcp list to confirm it was added. If missing, re-add it with /mcp add eConnect https://mcp.econnect.ai/mcp. |