voice integrated jarvis-like assistant with MCP
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"jarvis-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
TELEGRAM_SECRET_TOKEN=my-super-secret-webhook-token-2024
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / communication
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
Persistent memory using a knowledge graph
Dynamic problem-solving through sequential thought chains
MCP Security Weekly
Get CVE alerts and security updates for Jarvis Mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Your .env file should look like this:
# Bot token from @BotFather (this is your actual bot token)
BOT_TOKEN=7693362121:AAF3xxxxpL1K2rSw
# Create your own secret token for webhook security (any random string)
TELEGRAM_SECRET_TOKEN=my-super-secret-webhook-token-2024
# Your ngrok details
NGROK_AUTH_TOKEN=2xxX4vxxxxxShCNni69iTuS3PF8Vc
NGROK_URL=https://f071-101-127-95-132.ngrok-free.app
# Server configuration
PORT=3000
NODE_ENV=development
# For testing - your personal Telegram user ID (see instructions below)
TEST_CHAT_ID=123456789
RUN_INTEGRATION_TESTS=true
@userinfobot/help to your botuserId from the logs to your .env filesrc/
├── app.ts # Main entry point - starts server
├── controllers/
│ └── webhook.controller.ts # Handles Telegram webhook requests
├── services/
│ └── telegram/
│ └── telegram-bot.service.ts # Core bot logic and handlers
└── utils/
└── logger.ts # Logging utility
tests/
└── integration/
└── telegram-integration.test.ts # Integration tests
What each file does:
app.ts: Sets up Express server, initializes bot, configures webhooktelegram-bot.service.ts: Contains all bot commands and message handlerswebhook.controller.ts: Receives updates from Telegram and passes them to bot servicelogger.ts: Handles logging throughout the application# Install dependencies
npm install
# Make sure ngrok is running (in a separate terminal)
ngrok http 3000 --authtoken YOUR_NGROK_AUTH_TOKEN
# Option 1: Development mode with auto-restart
npm run dev
# Option 2: Build and run
npm run build
npm start
# Option 3: Direct TypeScript execution
npx ts-node src/app.ts
/help - should get help text and supported command list/status - should get runtime, GPT, Todoist, and activity status# Run integration tests (make sure your .env is properly configured)
npm test
# Or run tests with coverage
npm run test:coverage
Telegram → Webhook → ngrok → Your Server → Bot Service → Response → Telegram