Takos Office
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Takos OfficeCreate a new document titled 'Project Overview'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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")Related MCP server: Agentic AI System MCP Server
How it serves
One Cloudflare Worker, one Installation, three editor surfaces:
URL | Surface |
| document editor ( |
| presentation editor ( |
| spreadsheet editor ( |
| unified MCP (≈70 |
| 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.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tako0614/takos-office'
If you have feedback or need assistance with the MCP directory API, please join our Discord server