repaera/chat
Chat Client for Your Service's MCP Server
What's novel
Chat Client for Your Service's MCP Server
Code Analysis
16 files read · 4 roundsA production-grade, multi-platform AI chat application that connects to any MCP server for domain-specific tool use, supports 8 messaging platforms (Telegram, WhatsApp, Slack, Teams, GChat, Discord, GitHub, Linear), 9 LLM providers, image analysis/sharing, location sharing, and full i18n across 10 l
Strengths
Genuinely deep implementation with thoughtful production concerns: dual rate limiting (Redis + in-memory), platform-specific media pipelines, MCP JWT auth with mutual exclusivity validation, Azure-specific image prefetching, and a custom i18n system with IP geolocation and platform-native locale detection. The multi-platform bot system with /link account bridging is a novel and well-executed feature.
Weaknesses
The main chat route at 19kb could benefit from further decomposition, and test coverage is limited to schemas and rate limiting with no integration tests for the core LLM streaming, MCP tool calling, or bot platform flows. Some minor inconsistencies like Indonesian error messages in storage.ts and a few `as any` casts in the bot handler.
Score Breakdown
Signal breakdown
Innovation
Craft
Traction
Scope
Evidence
Commits
67
Contributors
2
Files
154
Active weeks
3
Repository
Language
TypeScript
Stars
14
Forks
1
License
NOASSERTION