Takos Office
Self-hosted productivity suite with document, slide, and spreadsheet editors, all accessible via a single MCP endpoint for agent-native interaction.
README
Takos Office
Takos Office is the Takos ecosystem's productivity suite — documents, slides, and spreadsheets
in one self-hostable worker, runnable inside your own Takos Workspace and agent-native through a
single MCP endpoint. It replaces the previously separate takos-docs, takos-slide, and takos-excel
apps, which are now folded into this one app.
It is the self-hosted, AI-operable alternative to Google Workspace / Microsoft 365 that you own.
Layout
takos-office/
app/
docs/ editor SPA + Hono routes (mounted at /docs) — formerly takos-docs
slide/ editor SPA + Hono routes (mounted at /slide) — formerly takos-slide
sheet/ editor SPA + Hono routes (mounted at /sheet) — formerly takos-excel
shared/ single copy of app-auth.ts, mcp-factory.ts, lib/takos-storage.ts
server.ts unified Hono worker (mounts the three editors + /mcp + /healthz)
mcp.ts unified MCP server (docs + slide + sheet tools on one endpoint)
build-worker.ts bundles the three SPA builds + the worker into dist/worker.js
site/ standalone marketing site (office.takos.jp)
docs/ roadmap
outputs.tf one OpenTofu app_deployment ("takos-office")
How it serves
One Cloudflare Worker, one Installation, three editor surfaces:
| URL | Surface |
|---|---|
/docs |
document editor (.takosdoc) |
/slide |
presentation editor (.takosslide) |
/sheet |
spreadsheet editor (.takossheet) |
/mcp |
unified MCP (≈70 docs_*/slide_*/sheet_* tools) |
/healthz |
readiness probe |
Each editor SPA is built with its own vite base (/docs/, /slide/, /sheet/) and SolidJS Router
base, so assets and routes resolve under the subpath. Storage stays the Takos Storage HTTP API
(folders /takos-docs/, /takos-slide/, /takos-excel/), unchanged.
Build
bun install
bun run build # 3 vite builds (build:spa) + unified worker (build:worker) → dist/worker.js
bun run check # tsc --noEmit
bun test # editor tests under app/*/src/__tests__
Run locally with bun run start (needs TAKOS_STORAGE_API_URL, TAKOS_ACCESS_TOKEN,
TAKOS_SPACE_ID, MCP_AUTH_TOKEN).
Boundary
Takos Office is one 1st-party Capsule app (jp.takos.office), seeded into new Workspaces as a
single Installation and removable as a whole. The three editors are no longer independently
installable — they are surfaces of this app. It remains substitutable: being "office" grants no
architectural privilege over Takos core. See AGENTS.md, docs/roadmap.md,
and the ecosystem AGENTS.md.
The former standalone repos (takos-apps/takos-docs, takos-apps/takos-slide, takos-apps/takos-excel)
are retired; their history lives in their own git remotes.
Site deploy
See site/DEPLOY.md.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。