SmartChats
SmartChats is a voice-first AI agent. You talk to it, and it can remember what you said, search the web, write and run code, and draw charts from your data. It reads and writes your data over the Model Context Protocol too, so other tools can use the same data.
The same agent runs two ways:
- Cloud: sign up at smartchats.ai. There is no server to run.
- Self-hosted: install with one command, then run
smartchats setupandsmartchats starton your laptop or a VPS. Same app, same agent. Your data stays in a database on your machine. See Quick Start.
Your data can move both ways. smartchats data export and
smartchats data import (and the matching MCP tools) copy everything
between cloud and local.
Voice logging and recall
The core use is simple. Through the day, talk to SmartChats from your phone or any device. Log thoughts, exercise, ideas, anything, in plain speech. It stores them as logs, metrics, todos and knowledge-graph facts.
Later, ask the built-in agent to recall it. Summarize the week. Find recurring themes. Compare what you logged on Tuesday with what you said on Friday. Draft a journal entry from your raw logs.
If you prefer another tool for the recall side, point Claude (or any
MCP client) or the smartchats CLI at your account. It is the same
data.
phone (voice in, all day)
│
▼
SmartChats stores
what you said
│
└─────────── your data (cloud or local) ─────────┐
│ │
▼ ▼
speak to SmartChats' (optional) Claude
agent for recall or any MCP clientThe other direction: bring data in, then talk to it
Any agent that speaks MCP can also write into your account. For example: point a coding agent at a folder of Markdown notes and have it write them into SmartChats as logs, metrics and knowledge-graph facts through the MCP server. Then ask SmartChats about them by voice.
your existing data agent reads and structures it
(Markdown, PDFs, exports) │
│ ▼
▼ MCP server writes into
any agent that your SmartChats account
speaks MCP │
▼
speak with it (SmartChats'
agent or any MCP client)Who it is for
Notes, decisions and half-formed ideas end up scattered across apps. Speak them to SmartChats as they happen, then ask its agent to recall them. It can pull patterns across weeks, list unfinished threads and connect last month’s logs to this week’s.
Get started
Install, run smartchats setup, and have a first conversation.
Environment, API keys, VPS deploys and the Docker alternative.
Self-HostingHow the app, agent, voice engine, servers and data layer fit.
ArchitectureConnect SmartChats to Claude Desktop or any MCP client.
MCP ServerWhat’s in the stack
- The app. A Next.js app in TypeScript that runs in your browser, with desktop and mobile layouts. The agent loop (cortex) streams structured output, runs code in a sandbox and keeps a knowledge graph.
- Voice. Speech recognition and voice activity detection in the browser (tivi), and streaming text-to-speech from the server. The vie voice engine is the default turn-taking engine. Before the main model answers, a small server-side turn judge decides whether you have finished speaking. See Voice engine.
- Model providers. OpenAI, Anthropic, Gemini, xAI and Together AI for chat, OpenAI and Azure for speech. Bring your own keys. See Providers.
- The local server (
smartchats-local-server). Serves the app and the/local-apiroutes against SurrealDB, including media upload and storage through any S3-compatible bucket such as SeaweedFS. See Local server. - The CLI (
smartchats). Sets up, starts and stops the local stack, signs in to the cloud, and imports and exports data. See CLI Reference. - The MCP server (
smartchats-mcp). Gives any MCP client your data over stdio. See MCP Server. - The hub and relay (
smartchats-hub,smartchats-mcp-bridge). Let coding agents on your machines talk with you through the app. See Hub and Relay.
The source for all of it is in the public repo, under the Apache License 2.0. See Architecture for what is open and what is closed.
See also
- GitHub issues for bugs and feature requests.
- LinkedIn (maintainer) for design discussions.
- Contributing for conventions and the dev workflow.