Language: English | 简体中文
GitHub: guchang/superinbox
Reducing capture friction is the core goal of SuperInbox.
When ideas appear, users should not have to think about which app to open first.
SuperInbox lowers the input barrier so you can capture anything quickly, while AI handles classification, extraction, and routing in the background.
- Multi-entry capture: Web, CLI, Bot, API, and MCP entry points.
- AI processing: Automatic classification and information extraction.
- Flexible routing: Route to Notion, Todoist, Feishu, and other downstream tools.
- Self-host friendly: Open-source core with local/private deployment support.
Scenario: Capture ideas instantly
Flow: Quick input → AI categorizes as
idea→ auto-save to Notion
Scenario: Forward links while browsing on mobile
Flow: Send to Telegram Bot → AI categorizes as
bookmark→ distribute to Notion
Scenario: Create tasks quickly
Flow: Input "Meeting at 3 PM tomorrow" → AI extracts time → create Todoist task
Scenario: Auto-categorized spending records
Flow: Input "Spent 25 yuan on coffee" → AI extracts amount/context → write to Feishu sheet
macOS / Linux:
./start.shStartup script automatically:
- ✅ Checks dependencies
- ✅ Detects port conflicts and offers handling options
- ✅ Starts backend and frontend services
Service URLs:
- Frontend: http://localhost:3001
- Backend API: http://localhost:3000/v1
# Check status
./start.sh status
# Stop services
./start.sh stop
# Restart services
./start.sh restartSuperInbox includes a companion CLI tool: sinbox. It is optimized for terminal-first and script-friendly capture workflows.
Quick example:
# Install CLI
cd ./cli
npm install
npm link
# Configure and verify
sinbox config
sinbox status
# Add and list
sinbox add "Meeting at 3 PM tomorrow"
sinbox listSee full CLI docs (bilingual): cli/README.md
SuperInbox publishes a stdio MCP server package: @superinbox/mcp-server.
- Start backend first (ensure
http://127.0.0.1:3000is reachable) - Add the server to your MCP config (replace API key as needed):
{
"mcpServers": {
"superinbox": {
"command": "npx",
"args": ["-y", "@superinbox/mcp-server"],
"env": {
"SUPERINBOX_BASE_URL": "http://127.0.0.1:3000",
"SUPERINBOX_API_KEY": "sk_xxx"
}
}
}
}Optional: pin to an exact package version for reproducibility:
{
"mcpServers": {
"superinbox": {
"command": "npx",
"args": ["-y", "@superinbox/mcp-server@<version>"],
"env": {
"SUPERINBOX_BASE_URL": "http://127.0.0.1:3000",
"SUPERINBOX_API_KEY": "sk_xxx"
}
}
}
}For local development/debugging, you can still run the source server directly:
{
"mcpServers": {
"superinbox": {
"command": "/path/to/SuperInbox/backend/node_modules/.bin/tsx",
"args": ["/path/to/SuperInbox/backend/src/mcp/server.ts"],
"env": {
"SUPERINBOX_BASE_URL": "http://127.0.0.1:3000",
"SUPERINBOX_API_KEY": "sk_xxx"
}
}
}
}- 中文主文档 - 项目中文介绍
- Startup Guide - unified startup guide
- Docs Index - documentation entry point
- SuperInbox Core API - backend APIs
- SuperInbox CLI (Bilingual) - CLI setup, commands, and FAQ
- MCP Server Package - npm MCP setup and troubleshooting
SuperInbox/
├── backend/ # Backend service (Express + SQLite)
├── web/ # Frontend app (Next.js + React)
├── cli/ # CLI tool
├── packages/ # Publishable packages (including MCP server)
├── start.sh # Bash startup script
├── start.js # Node.js startup script
└── README.md # English README (this file)
Default ports:
- Backend: 3000
- Frontend: 3001
Custom ports:
BACKEND_PORT=8080 FRONTEND_PORT=8081 ./start.sh- Node.js >= 18.0.0
- npm
- macOS / Linux / Windows
MIT