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
project-nova
Manages Paperless-NGX documents by providing an MCP server that exposes an SSE endpoint for integration with n8n, enabling AI agents to search, upload, and manage documents, tags, correspondents, and document types.
fast-mcp-telegram
Enables AI assistants to interact with Telegram for messaging, search, and contact management via a standardized MCP interface.
n8n-skills
Provides expert guidance for an AI assistant to build and manage n8n workflows, covering JavaScript and Python code, expressions, validation, node configuration, and architectural patterns, with a focus on AI agents within n8n.
One-Stop-Shop-N8N-MCP
n8n workflow automation and intelligent assistance, leveraging AI (LLMs, GraphRAG) for design, generation, validation, and management of integration workflows.