elasticsearch_mcp_n8n_telegram_bot
Verified Safeby Som23Git
Overview
AI-powered conversational expense tracking and querying via Telegram, leveraging AWS Bedrock LLMs and Elasticsearch's Agent Builder for ingestion and retrieval.
Installation
No command providedEnvironment Variables
- TELEGRAM_BOT_TOKEN
- SARVAM_ENDPOINT
- SARVAM_API_KEY
- AWS_ACCESS_KEY_ID
- AWS_SECRET_ACCESS_KEY
- AWS_REGION
- ELASTICSEARCH_API_KEY
- ELASTICSEARCH_CLOUD_URL
- ELASTICSEARCH_INDEX_NAME
Security Notes
The system relies on n8n's credential management for sensitive API keys (Telegram, AWS, Elasticsearch, Sarvam STT), which is a good practice. LLM outputs are explicitly parsed for JSON objects with custom code, avoiding dangerous functions like `eval`. A hardcoded user ID is used for access control, which is basic but effective for a personal bot. The `_example.json` shows placeholders, emphasizing the need for secure configuration over hardcoding. General LLM hallucination is acknowledged as a risk.
Similar Servers
mcp-n8n-builder
Programmatically create, manage, and monitor n8n workflows and their executions via an MCP server, allowing AI assistants to automate workflow development without direct user intervention.
project-nova
Manages digital documents, tags, correspondents, and document types within a Paperless-NGX instance via a containerized MCP server using SSE transport for n8n integration.
fast-mcp-telegram
Provides a production-ready Telegram integration for AI assistants with comprehensive search, messaging, and direct API access capabilities.
One-Stop-Shop-N8N-MCP
This server acts as an intelligent n8n workflow co-pilot, leveraging dual nano LLMs and a GraphRAG knowledge base for intent-driven query routing, automated workflow generation, and validation.