Takos Office
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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.
What you can do
write documents, slides, and spreadsheets in three editors served from one Worker
import and download normal Microsoft Office files:
.docx,.pptx, and.xlsxlet an agent operate all three editors through a single MCP endpoint at
/mcpkeep every file in your own object storage — the app consumes
storage.object, it does not host your datainstall it as one Capsule, or run it yourself with
bun run start
Related MCP server: pharos-ai-doc-genie
Getting started
bun install
bun run build # 3 vite builds + unified worker -> dist/worker.js
bun run start # run it locallyStandalone HTTP storage needs OBJECT_STORAGE_API_URL,
OBJECT_STORAGE_ACCESS_TOKEN, and a storage namespace (TAKOS_SPACE_ID).
For browser storage managed by Takosumi, configure the explicit HTTPS
TAKOSUMI_CONTROL_API_URL, app-scoped OIDC sign-in, APP_CAPSULE_ID, and a fixed
APP_WORKSPACE_ID/TAKOS_SPACE_ID. The root manifest requests the four
storage.object.* permissions using the explicit oauth2.app-data.v1 delivery.
Each request revalidates its signed-in person; every object operation obtains a
new exact-permission token with dataScope: "app-shared.v1". No invocation token
is written into frontend storage or cached across people. Failed or invalid
runtime configuration never falls back to the standalone bearer.
The root module exposes takosumi_control_api_url as a visible explicit input.
It retains an empty HCL default for existing standalone callers. An
app-authenticated Worker without explicit standalone Storage is refused by a
resource precondition until this URL is supplied, before resources can be changed. The URL is not inferred from Accounts, request Host, or outputs.
An operator must explicitly permit these four storage permissions and this
new delivery profile; the default launcher/MCP-only policy intentionally refuses
it. Normal provider selection and approval remain required.
Use an artifact built from this updated source. The existing v0.3.1 release
pin is unchanged and does not prove the new runtime consumer is deployed.
Existing Binding-scoped objects are not copied into the new app namespace;
changing a live connection needs an explicit data migration/cutover. Browser
app-session delegation does not turn an incoming MCP invocation bearer into an
Office app login: cookie-less MCP storage delegation and portable-module runtime
configuration remain separate follow-ups. MCP retains its explicit standalone storage configuration even when browser
runtime storage is enabled. It does not use the new app namespace: the two routes
must not be assumed to see the same data without a separate migration/delegation
plan. No managed/live readiness is claimed by the local proof.
In runtime storage mode /health and /healthz validate configuration only and
return storage: "per_request_authorization", storageProbed: false; anonymous
probes never acquire person credentials or claim the backend is reachable. Each
signed-in operation performs the actual authorization/storage checks. Standalone
readiness retains its existing authenticated object-list probe.
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 and the mcp.tools interface spec
design.md locked design system for the editors — tokens.css is its runnable export
outputs.tf ordinary runtime URLs used by reviewed Interface requestsRuntime contract
Takos Office publishes the Office Suite launcher and unified MCP endpoint and consumes an object-storage service.
The root module in .well-known/takosumi.json requests the launcher at /, the MCP Interface at /mcp, and the
installing principal's ui.open / mcp.invoke bindings. Takosumi validates these requests against operator policy
and compiles them into its DB-owned InstallConfig.interfaceBlueprints. The ordinary OpenTofu outputs alone
grant no access and do not create a launcher.
Direction | Service identity / capability |
publish |
|
publish |
|
consume |
|
How it serves
One Cloudflare Worker, one Capsule install unit, three editor surfaces:
URL | Surface |
| suite home, recent files, and cross-editor search |
| document editor with |
| presentation editor with |
| spreadsheet editor with |
| cross-app recent / search for host integrations |
| unified MCP (≈80 |
| readiness probe |
The suite recent/search APIs return items, plus unavailableApps when reads
partially fail. Healthy editors
remain visible if another editor cannot be read; the home page marks these results
as incomplete and offers an explicit retry. If all three reads fail, the API
returns 503 and the home page shows a load error instead of claiming there are no files.
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 object-storage HTTP API
(folders /takos-docs/, /takos-slide/, /takos-excel/), unchanged.
Docs retains title and content edits in the current Workspace's browser cache before its 500 ms autosave delay. Reloading during that delay restores an Unsaved draft with explicit save/discard recovery; it does not silently replay a write. A pending request whose acknowledgement was lost remains Save unconfirmed, even after further typing. Both paths keep the existing server revision checks and require a fresh read for explicit replacement.
On phone screens, Docs places its collapsible outline above the document and gives the title its own row. Compact screen gutters keep text readable. The desktop outline retains its separate collapse preference and releases the sidebar space when collapsed. Choosing a heading focuses its text and scrolls that heading into view; on phones it also closes the outline.
Docs library and editor reads belong to the view that started them. Leaving and reopening that Workspace retires the earlier read: its result cannot update the reopened cache, erase its draft/journal on a late 401, or redirect the new view. A 401 for the current view still clears that scope and starts sign-in; retained drafts do not replace authorization.
Opening or creating a document and returning to the Docs library preserve the
active Workspace in the URL, so reloading keeps API reads in that Workspace.
Both space_id and spaceId entry URLs are supported; standalone URLs remain
usable without adding a Workspace identifier.
Slides and Sheets also retain the Workspace across library/editor navigation, including creation and error recovery. Slides keeps it when starting a presentation, leaving with Escape, or exiting fullscreen. Sheets sends a create-only condition when saving a new spreadsheet. Both editors wait for the create acknowledgement before opening the new item. An unconfirmed create is retained for its Workspace across route changes and remounts until a successful library read, without resending it.
Sheets serializes saves for each spreadsheet against acknowledged server revisions. Its cache and pending-write journal belong to the selected Workspace. Conflicts and unknown acknowledgements retain the local draft, including across reload, and block automatic replay. Recovery offers a fresh conditional replacement or an explicit read/discard; a concurrent writer can still reject the replacement. Tab operations use the same revision queue, and deletion removes a local item only after an explicit successful deletion acknowledgement. An explicit replacement in Docs, Slides or Sheets that is cancelled before its queued write starts keeps the local draft for another explicit recovery. Cancellation after dispatch does not undo the write or replace its actual acknowledgement. Formula-bar typing retains its own focus; each Enter commits the edit once. Typing with an IME into a selected cell opens the inline editor. Conversion confirmation keeps the draft; a subsequent explicit Enter saves it. The new spreadsheet dialog also waits for conversion before creating the file.
The native input regression uses an isolated Chrome profile and trusted IME input:
node scripts/smoke-sheet-ime.mjs /path/to/chrome (Node 24+). It is separate from
the portable gate. Its callback/request fixture refuses API writes and does not
qualify storage, a physical OS keyboard, or an installed app.
Use the optional slide argument to check the actual presentation creation dialog
without repeating the spreadsheet cases.
Slides and Sheets library reads also retire with their captured view, including leaving and reopening the same Workspace. Late reads cannot reinsert a deleted item into the reopened cache or clear that cache on an old 401. Current-view 401 refusals still invalidate that scope and its pending-write journal.
Slides uses the same acknowledged-revision queue and Workspace-bound cache/journal. Continuous edits and late responses preserve newer drafts. Unknown saves or true conflicts retain the draft across reload and expose explicit conditional recovery; opening presentation mode also keeps the current Workspace. Library deletion keeps the item until an explicit successful deletion acknowledgement. The new presentation dialog keeps Japanese input through IME conversion; only a subsequent explicit Enter creates the file with its final title.
Office file compatibility
The standard Office formats are exchange formats; the private JSON model remains the lossless editing state used for autosave, collaboration fencing, and MCP.
Editor | Import / download | Preserved common content |
Docs |
| paragraphs, headings, lists, tables, links, common inline formatting, and embedded raster images |
Slides |
| slide order and size, text, common shapes, embedded raster images, backgrounds, and speaker notes |
Sheets |
| worksheets, values, formulas with cached results, common cell formatting, and row/column sizes |
Import is deliberately bounded to 25 MiB compressed, 100 MiB expanded, and 10,000 ZIP entries; converted editing state must fit 7 MiB. Slides retains at most 5 MiB of embedded raster image bytes per imported deck. Sheets additionally accepts at most 1,000 rows, 100 columns, and 10,000 populated cells. Macros, charts, SmartArt, animations, grouped slide objects, and other advanced Office constructs are not claimed as pixel-perfect; unsupported content is omitted or reduced to a safe fallback rather than silently being treated as lossless.
Docs exposes Word import in its library and Word download in the editor's Export menu. A new import is created only after file conversion succeeds and opens only after the ordinary create-only API acknowledges it. Conversion and its eventual request/cache destination belong to the Workspace where the file was selected; leaving that view retires its UI result. An unconfirmed write retains the usual explicit draft recovery instead of silently retrying the import.
Word conversion runs in a disposable browser Worker with a 15-second budget. Archives with encrypted content, macros, embedded executable objects, XML entity declarations, duplicate/aliased parts, broken checksums, or external image/resource relationships are rejected. Ordinary safe hyperlinks are retained without fetching them. XML/editor trees are bounded to 100,000 nodes and depth 128, and embedded raster dimensions are bounded to 32 million pixels in total. The original Word file is never executed or attached as HTML. Page layout, custom fonts and advanced Word features are not guaranteed to round-trip; keep the original file for fidelity.
Slides exposes PowerPoint import in its library and a PowerPoint download button in the editor. Conversion uses the same disposable Worker deadline, safe package admission, Workspace capture, and create-only acknowledgement rules as Word. Imported page dimensions are retained as exact EMUs through save/reload, editor and thumbnail rendering, presentation mode, PNG, PDF, and PPTX export. Decks without this metadata retain the previous 16:9 editing space and PDF convention. Embedded PNG, JPEG, GIF, and BMP images share a 5 MiB decoded-byte and 32 million pixel budget per deck; remote images are never fetched during PPTX conversion. Server PDF/PNG export checks raster magic, declared MIME and dimensions before decoding, with the same 5 MiB image-byte and 32 million pixel budget shared by inline and remote images. PNG, JPEG, GIF, BMP and WebP remain supported. Images that fail admission use the existing placeholder. Loading is sequential and repeated URLs, including failed loads, are reused within an export. There is no new 64-image limit; these image budgets do not establish a service-wide capacity or a total export deadline across distinct failed URLs. MCP PDF/PNG rendering propagates the authenticated HTTP request signal and the SDK tool cancellation signal to image fetch/read and checks it before later image decodes, placements and output. Cancellation is cooperative: an already running synchronous codec or output operation is not preempted, and callers that do not cancel still have no new total export deadline. This does not add cancellation-notification routing across separate stateless HTTP requests or qualify disconnect signaling in a deployed runtime. Slides accepts at most 1,000 slides, 10,000 elements per slide, and 50,000 elements in total. Common text, basic shapes, raster images, backgrounds, and speaker notes are converted; rich text, theme/layout detail, charts, groups, transitions and other advanced constructs can be simplified or omitted with a warning. Unsafe embedded objects and external resource relationships are refused before a new presentation is created. Keep the original PowerPoint file when layout fidelity matters.
Sheets exposes Excel import in its library and an Excel download action in its editor. The same disposable Worker, bounded package admission, original Workspace capture and create-only acknowledgement rules apply. Literal text, numbers, booleans and errors keep their types; shared formulas, cached results, common font/fill/alignment and number formats, and row/column sizes are retained. 1904 date workbooks normalize into the editor's existing date system. Defined names stay symbolic metadata and are retained for Excel rather than expanded into cell allocations during import. For workbooks with names, row/column insert or delete and sheet rename or delete are explicitly refused: use Excel for those structural edits until reference rewriting is supported. Values and formatting remain editable. Merge expansion is bounded before the codec; unsupported data validations are omitted before their ranges can be expanded.
Opening or formatting an imported workbook keeps its saved formula results and shows that they came from the file. Explicit value or structural changes mark imported caches across sheets as out of date. The existing calculation engine recalculates supported formulas; unsupported formulas may need Excel. Stale caches are not written as current results, and exported workbooks request a full recalculation in Excel. Cached values are not evidence of a new calculation. Unsafe external/DDE/network formulas and unsafe hyperlink targets are refused. Custom fonts, theme colors, merged layouts, validation, charts, rich text and other advanced features may be simplified with a warning. Keep the original workbook for full fidelity; the JSON editing state is not a lossless Excel engine.
OpenTofu outputs and first apply
The four Interface source URLs are ordinary root-module outputs:
Output | Runtime surface |
| unified Streamable HTTP MCP resource |
| Docs UI |
| Slide UI |
| Sheet UI |
Takos Office keeps a private JSON model in Takos Storage as its lossless
editing state. The native .takosdoc, .takosslide, and .takossheet record
names are storage implementation details and recovery compatibility, not
end-user formats or published file-handler Interfaces.
launch_url / url / public_url remain normal deployment convenience outputs. app_deployment and
service_exports are retired and are not runtime registries.
The Repository manifest uses takosumi.com/v2.5 to request the current Workspace
and Capsule IDs as noneditable context data for the existing root string inputs.
Use an installer that supports v2.5 and select module . explicitly; the existing
Cloudflare Source option retains that path. The legacy defaultModule hint is
not part of v2.5. These selectors carry no literal ID, credential, or grant, and
they do not change the portable module's contract.
Managed installation requires the authenticated Capsule context to supply the non-secret Workspace id in
object_storage_workspace_id and the Capsule id in app_capsule_id; the Worker Plan rejects a missing owner
context. The module injects them into the Worker as
APP_WORKSPACE_ID and APP_CAPSULE_ID (and keeps TAKOS_SPACE_ID for the storage namespace). Interface ids and
resolved revisions do not exist until after apply, so they are deliberately not module variables or Worker env.
MCP authentication
Managed /mcp calls use short-lived InterfaceBinding OAuth credentials with the exact mcp.invoke permission and
mcp_url audience. For every request, the Worker sends the bearer to Takosumi Accounts UserInfo. Accounts first
revalidates current Interface and Binding state; the Worker then requires all of the following from the 200 response:
token_use: "interface_oauth", a non-emptysub, exactaud, and exact singlescope;exact
takosumi.capsule_id; an optionaltakosumi.workspace_id, when present, must match the configured namespace (APP_WORKSPACE_IDorTAKOS_SPACE_ID);non-empty
interface_idandinterface_binding_id, plus a positiveinterface_resolved_revision.
The check is fail-closed, follows no UserInfo redirects, and keeps no static Interface id/revision pin. An explicitly
provided mcp_auth_token is still accepted as MCP_AUTH_TOKEN for direct/self-host standalone use only. Empty input
creates no standing MCP credential, and no credential is exposed through an Output.
Build
bun install
bun run build # 3 vite builds (build:spa) + unified worker (build:worker) → dist/worker.js
bun run check # format/type/tests/3 SPA builds/worker build + artifact-size gate
bun audit # high/critical dependency advisory gate
bun test # editor and worker tests under app/**/__tests__Run locally with bun run start. Storage needs OBJECT_STORAGE_API_URL, OBJECT_STORAGE_ACCESS_TOKEN, and a
Workspace (TAKOS_SPACE_ID). For MCP, either provide an explicit standalone MCP_AUTH_TOKEN, or configure
APP_URL, OIDC_ISSUER_URL, APP_WORKSPACE_ID, and APP_CAPSULE_ID for Interface OAuth. Unauthenticated MCP is
available only through the explicit local/dev MCP_ALLOW_UNAUTHENTICATED escape hatch.
dist/worker.js is generated output for local/self-host applies. Hosted
Takosumi installs should pass worker_bundle_url + worker_bundle_sha256 from
a Git release or CI artifact. Do not commit the built worker or SPA output to
the repository.
install-options.json is the optional source chooser.
The separate general
.well-known/takosumi.json Repository manifest
proposes input names and presentation projections for the root direct module and
deploy/takoform from the same Git commit. Neither document carries secrets,
provider credentials, Cloudflare account authority, Interface grants, or
execution authority. Interface and binding declarations are requests, not realized grants. Takosumi validates
the proposal and compiles it into a DB-owned InstallConfig before the ordinary Plan and Apply lifecycle.
Boundary
Takos Office is one installable Capsule app (jp.takos.office). It can be
added explicitly from a Store or Git install link and removed 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,
design.md, the mcp.tools interface spec,
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.
Current-source Takoform Host module
The Takoform Host source option selects deploy/takoform-v1 and Provider
4.0.0. It builds the selected Git source, stages dist/worker.js, and publishes
one ModuleWorker/Bundle/Version/Deployment/Endpoint graph. It does not select the
old v0.3.1 release pin. The older deploy/takoform module is kept unchanged; this
is a separate module, not a state migration or an in-place provider upgrade.
Enter the explicit Takosumi Core API URL. Current app and internal storage IDs
come from the selected install context. Session-secret and OIDC binding names
are compiled through the current runtime-binding v2 profile, with no credential
values in HCL or public metadata. The host supplies the exact registered
OIDC_REDIRECT_URI before activation; Office uses it for login/token exchange
and derives the public MCP audience from that configured URI when APP_URL is
absent. An invalid declared URI or conflicting explicit app origin returns 503;
it never falls back to request Host. Owner-subject delivery does not add an
owner-only content rule: current app owner/member authorization is preserved.
launch_url is an ordinary endpoint output used by the reviewed launcher
Interface. It is not fed into WorkerVersion or OIDC configuration, so it creates
no post-apply URL cycle. A compatible Host, its private runtime inputs and an
explicit policy permitting the Storage app-data profile remain necessary.
Source/local tests are not proof of a configured Host, provider Plan/Apply, or
installed service. This module advertises the Suite launcher only. MCP
shared-data delegation is not implemented, so this module does not publish an
MCP Interface or MCP endpoint output. Existing-object migration also remains
open as described above.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Online office suite for AI agents: edit docs, sheets, slides and PDFs in browser or via MCP.
An agent-first office suite Claude & ChatGPT read and write over one MCP URL.
Agent-native notes, tasks, dev-docs, vaults, sync & handoffs. MCP + OpenAPI dual surface.
Self-hosted AI workspace: semantic RAG document search, long-term memory, and AI chat via MCP.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA self-hosted MCP server for managing email, calendar, and cloud storage across Microsoft 365, Google Workspace, and IMAP accounts, enabling natural language interaction through any MCP client.1MIT
- AlicenseAqualityDmaintenanceEnables AI agents to generate real Office documents (.pptx, .docx, .xlsx) and source code from natural language via MCP protocol.4MIT
- AlicenseNot gradedqualityBmaintenanceSuite of MCP servers for local-first, governed automation of Microsoft Office files (Excel, PowerPoint, Word) via structured tool calls.8MIT
- AlicenseNot gradedqualityBmaintenanceLocal-first personal productivity MCP server bundling email, calendar, messaging, search, and image generation tools with BYOK and no cloud dependency.85 npmMIT