MCP Server Ecosystem
LARS doesn't just answer questions. LARS takes action through integrated tools.
Core MCP Servers
| Server | Purpose | Example Actions |
|---|---|---|
| Voice | TTS/STT | Speak responses, take voice input |
| Document | File management | Create PDFs, read uploads |
| Corpus | Content extraction | Ingest documents, index content |
| Track | Project management | Create tasks, track progress |
| Contact | CRM | Manage contacts, track leads |
| KB | Knowledge base | Store/retrieve documentation |
| Context | Memory | Save learnings, session context |
| Links | URL management | Save/enrich bookmarks |
| Locker | Credentials | Secure storage for secrets |
| Chrono | Time/Weather | Greetings, scheduling |
| Workflow | Protocols | Patterns, behaviors |
Temp Environment for Work
LARS needs scratch space for complex tasks: - Draft documents before finalizing - Stage data for processing - Build outlines iteratively - Hold intermediate results
User: 'Create an outline from my seven books'
LARS process:
1. Query Corpus for all book content
2. Create outline draft in Temp
3. Iterate and refine
4. Move final to Documents
5. Optionally save to KB
Gateway Architecture
All tools accessed through single Gateway: - One connection point - Parallel batch calls - Hot-reload capability - No context loss on updates
Client Deployment
Tool selection based on client needs: - Law firm: Corpus, Document, Contact heavy - Creative agency: Voice, Document, KB - Sales team: Contact, Track, Links - All clients: Core platform + customization