Skip to content

armgit / mso

Public Imported from GitHub
0

Browser-based graphical shell and control plane for a Linux server you own — real terminal, file manager, live metrics and BYOK AI in one mobile-first workspace. Next.js 16 · React 19 · node-pty · Tailwind v4 · shadcn/ui. Public alpha, self-hosted.

docs(mcp): add README quickstart and practical how-to

Rahman7cffd1114966
diff --git a/README.md b/README.md
index baf5741f..8a34b174 100644
--- a/README.md
+++ b/README.md
@@ -1,7 +1,7 @@
<h1 align="center">Manef Shell OS</h1>
<p align="center"><strong>A workspace for your server. A runtime for your agents.</strong></p>
<p align="center">Real terminals, project-aware AI, files and services — in one self-hosted workspace.</p>
-<p align="center"><a href="#see-it-work">Demo</a> · <a href="#install-or-update-mso-from-this-repo">Install</a> · <a href="./docs/COGNITIVE-RUNTIME.md">Agent runtime</a> · <a href="./docs/README.md">Docs</a></p>
+<p align="center"><a href="#see-it-work">Demo</a> · <a href="#install-or-update-mso-from-this-repo">Install</a> · <a href="./docs/COGNITIVE-RUNTIME.md">Agent runtime</a> · <a href="./docs/MCP-HOW-TO.md">Use MCP</a> · <a href="./docs/README.md">Docs</a></p>
<p align="center"><a href="https://github.com/rahmanef63/mso/actions/workflows/ci.yml"><img alt="Tests and build" src="https://github.com/rahmanef63/mso/actions/workflows/ci.yml/badge.svg" /></a> <a href="https://github.com/rahmanef63/mso/actions/workflows/security-alerts.yml"><img alt="Actual open security findings" src="https://github.com/rahmanef63/mso/actions/workflows/security-alerts.yml/badge.svg" /></a></p>
## See it work
@@ -68,6 +68,30 @@ Browser reset is separate in **Settings → About**. [Backups, scope and safegua
</details>
+## Use MSO from an AI app (MCP)
+
+Connect ChatGPT, Codex, Claude Code, Cursor, or another compatible MCP client to your
+MSO installation. **You do not need SI-Coder**: it is an optional MSO plugin, not the
+MCP server or an installation prerequisite.
+
+1. Open **Settings → MCP → Access MSO → Connect an app** and choose your client.
+2. Copy the server URL shown there (`https://mso.example.com/mcp` is a placeholder),
+ select **OAuth**, and authorize on an approved MSO owner device.
+3. Grant the minimum useful scope, refresh/scan the client's tools, and enable MSO
+ in the conversation. Start with: `@MSO check server status without changing anything`.
+
+| Direction | What it does |
+|---|---|
+| **Access MSO** | Your AI app → MSO → permitted server/project operations. |
+| **MSO Access** | MSO → external services/project MCPs with separately configured credentials. |
+
+Fresh installs enable MCP with an `exec` ceiling; existing installs preserve their settings.
+`read` observes, `write` adds bounded changes, and `exec` permits host/delegated execution.
+A ceiling is not a grant: actual token scope and server guards still apply. Lower the ceiling
+when shell access is unnecessary. Never paste passwords or tokens into a prompt.
+
+[How to use MCP — Bahasa Indonesia](./docs/MCP-HOW-TO.md) · [ChatGPT setup/reference](./docs/CHATGPT-PLUGIN.md) · [Protocol and security](./docs/MCP.md) · [Generated tool catalog](./docs/generated/MCP-CATALOG.md)
+
## Build with it
```bash
diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md
index b2fbd632..f70fa602 100644
--- a/docs/CHANGELOG.md
+++ b/docs/CHANGELOG.md
@@ -21,6 +21,10 @@ this is the *what*, and it is what Settings → About shows as “What's new”.
- `ui` constrain simulated host message origins
+**Docs**
+
+- `mcp` add README quickstart and practical how-to
+
## 2026-09-11
**Added**
diff --git a/docs/CHATGPT-PLUGIN.md b/docs/CHATGPT-PLUGIN.md
index 0c87bf81..86ce5f6f 100644
--- a/docs/CHATGPT-PLUGIN.md
+++ b/docs/CHATGPT-PLUGIN.md
@@ -1,5 +1,7 @@
# ChatGPT custom MCP app for MSO
+For first-time setup and copyable usage examples, start with [How to use MSO MCP](./MCP-HOW-TO.md).
+
> **Current ChatGPT-facing reference.** MSO is one open-source MCP server. ChatGPT receives a deliberately compact static projection of MSO-owned generic tools; project-owned MCP tool names are never copied into the global catalog or ChatGPT scan snapshot.
>
> ChatGPT's Developer Mode/App UI can change independently of MSO. Use the current OpenAI MCP/App documentation for exact menu labels, and use MSO Settings → MCP / `GET /mcp` for the live server/profile signatures.
@@ -56,7 +58,7 @@ The restored Original MSO operator primitives (`sys_*`, `fs_usage` + full bounde
Project-owned MCP names and Convex's own dynamic schemas still load on demand through `project_mcp_tools` / `project_mcp_call` and `project_database_tools` / `project_database_call`. That is how MSO keeps a bounded static model profile instead of copying every downstream provider/project action into ChatGPT.
-ChatGPT presentation is explicit rather than attached to every operation. `workflow_start` is headless. `render_mso_block` opens the compact validation/action/CRUD component and accepts only bounded fields, checks, outputs, and follow-up actions; a button cannot execute a mutation inside the widget. `render_mso_page` opens native MSO views or a code-reviewed development/preview/production app. It accepts only MSO-style routes and server-owned app ids, never arbitrary HTML or an external URL. `mso_surface_apps_list` exposes the reviewed Page catalog. External apps use the remote browser; Page does not mount third-party iframes. User-installed runtime HTML apps do not inherit this trust automatically. `render_mso_surface` and `workflow_status` remain app-only compatibility shims for cached clients.
+ChatGPT presentation is explicit rather than attached to every operation. `workflow_start` is headless. `render_mso_block` opens the compact validation/action/CRUD component and accepts only bounded fields, checks, outputs, and follow-up actions; a button cannot execute a mutation inside the widget. `render_mso_page` opens native MSO views or a code-reviewed development/preview/production app. It accepts only MSO-style routes and server-owned app ids, never arbitrary HTML or an external URL. `mso_surface_apps_list` exposes the reviewed Page catalog. Apps outside the reviewed Page catalog use the remote browser. Nested frames are limited to code-reviewed exact origins and registry policy; arbitrary third-party URLs are never accepted. User-installed runtime HTML apps do not inherit this trust automatically. `render_mso_surface` and `workflow_status` remain app-only compatibility shims for cached clients.
`render_mso_page` and `integration_setup_open` bind Page through the standard MCP Apps `ui.resourceUri` field only. Do not mirror `openai/outputTemplate` onto Page tools: the current ChatGPT host already supports the standard binding, and dual Page bindings can mount the same UI twice. The current Page therefore uses one modern binding and keeps earlier Page URIs only as non-advertised read aliases.
@@ -85,7 +87,7 @@ projects_list
↓
project_capabilities
↓
-project_mcp_tools(project, server) # exec: initializing project MCP executes project code
+project_mcp_tools(project, server) # exec: may start project code or contact a remote service
↓
project_mcp_call(project, server, tool, arguments)
```
@@ -153,7 +155,7 @@ MSO uses Streamable HTTP JSON-RPC over `POST /mcp`.
4. Choose OAuth and complete the MSO consent flow on an approved owner device.
5. Select the lowest useful MSO tier. After changing `OS_MCP_MAX_SCOPE`, rebuild/restart MSO and repeat consent so the connector receives the new ceiling.
6. Run **Scan Tools / Refresh** in ChatGPT.
-7. Verify that the action snapshot corresponds to the 66-tool transport profile (64 model-visible actions + app-only `workflow_status` and `render_mso_surface`) in the generated catalog.
+7. Compare the action snapshot with the current scope-filtered ChatGPT profile in the [generated catalog](./generated/MCP-CATALOG.md) and the live `GET /mcp` signature. Do not rely on a fixed historical tool count.
8. Start a new chat when testing a newly scanned draft/action snapshot.
After a schema/profile change, changing production code alone does not replace ChatGPT's frozen action snapshot. Refresh/re-scan (or recreate/republish where the workspace UI requires it) after deployment.
diff --git a/docs/MCP-HOW-TO.md b/docs/MCP-HOW-TO.md
new file mode 100644
index 00000000..fac45593
--- /dev/null
+++ b/docs/MCP-HOW-TO.md
@@ -0,0 +1,190 @@
+# How to use MSO MCP
+
+Panduan praktis berbahasa Indonesia: hubungkan AI ke MSO, jalankan tugas pertama,
+dan periksa masalah koneksi. Untuk instalasi MSO, mulai dari [README](../README.md).
+Nilai `mso.example.com`, `example-project`, dan `<workflow-id>` hanyalah placeholder.
+
+## 1. Pilih arah koneksi
+
+| Menu di Settings → MCP | Arah dan fungsi |
+|---|---|
+| **Access MSO** | ChatGPT/Codex/klien lain → MSO. Gunakan untuk mengelola server dan proyek melalui AI. |
+| **MSO Access** | MSO → layanan eksternal. Registry plugin dan koneksi proyek tidak otomatis memberikan izin ke layanan tersebut. |
+| **Sessions** | Lihat sesi, aktivitas, dan informasi handover; bukan pengaturan scope token. |
+
+SI-Coder adalah **plugin opsional MSO**, bukan server MCP utama atau syarat memakai MSO.
+Menambahkan manifest ke **Plugins / Registry** hanya menyimpan deklarasi di browser;
+itu tidak menginstal kode, mengaktifkan koneksi, atau membuat credential.
+
+## 2. Siapkan MSO
+
+Masuk ke MSO dengan perangkat Owner yang sudah disetujui. Buka
+**Settings → MCP → Access MSO → Connection details** untuk URL dan pemeriksaan koneksi.
+Klien cloud membutuhkan origin HTTPS stabil yang dapat dijangkau, bukan localhost
+atau URL Quick Tunnel sementara. [Panduan instalasi dan HTTPS](./INSTALL.md).
+
+Instalasi baru mengisi `OS_MCP_ENABLED=1` dan `OS_MCP_MAX_SCOPE=exec`.
+Update mempertahankan `.env.local` lama. MCP yang dinonaktifkan atau mode demo menghasilkan 404.
+Untuk membatasi instalasi menjadi observasi saja, ubah **dua nilai terkait saja** di `.env.local`:
+
+```dotenv
+OS_MCP_ENABLED=1
+OS_MCP_MAX_SCOPE=read
+```
+
+Jangan mengganti seluruh `.env.local`. Terapkan perubahan melalui **Settings → About**
+atau `mso update --rebuild`, lalu ulangi otorisasi bila scope koneksi perlu berubah.
+
+| Scope | Pemakaian |
+|---|---|
+| `read` | Status, daftar proyek, dan pembacaan yang dibatasi. |
+| `write` | Semua kemampuan read ditambah perubahan terbatas. |
+| `exec` | Semua kemampuan write ditambah shell dan eksekusi/delegasi proyek. |
+
+`OS_MCP_MAX_SCOPE` adalah batas maksimum; izin token aktual tetap diperiksa pada setiap call.
+Pilih scope sesuai tugas: jangan menyebut seluruh MSO read-only hanya karena satu call ditolak.
+`exec` dapat menjalankan perintah sebagai user layanan MSO; jangan berikan tanpa kebutuhan.
+
+## 3. Hubungkan klien
+
+### ChatGPT
+
+1. Di MSO, pilih **Access MSO → Connect an app → ChatGPT** dan salin Server URL.
+2. Aktifkan Developer Mode di ChatGPT bila diperlukan. Dokumentasi OpenAI saat ditinjau
+ memakai **Settings → Security and login**, lalu **Plugins → +**; workspace lama bisa
+ menampilkan Apps/Create. Izin admin workspace tetap berlaku.
+3. Buat app MCP dengan URL **`https://mso.example.com/mcp`**, transport **Streamable HTTP**,
+ dan autentikasi **OAuth**. Gunakan domain instalasi sendiri, bukan `/api/mcp` atau `/sse`.
+4. Selesaikan login/consent pada domain MSO dan pilih scope minimum. Gunakan discovery/DCR
+ bila tersedia; untuk form Client ID manual, MSO mendukung `chatgpt-mso` tanpa client secret.
+ Jangan memasukkan password MSO sebagai client secret dan jangan memilih No Authentication.
+5. Scan/refresh tools, simpan/publikasikan sesuai UI workspace, lalu aktifkan MSO pada percakapan.
+6. Uji dengan `@MSO tolong cek status VPS tanpa mengubah apa pun`.
+
+`@MSO` adalah nama app yang dipilih; penyebutan nama saja bukan bukti koneksi berhasil.
+Bukti awal adalah tool benar-benar dipanggil dan mengembalikan hasil, bukan jawaban tebakan AI.
+Lihat [referensi ChatGPT](./CHATGPT-PLUGIN.md) untuk detail OAuth dan refresh.
+
+### Codex dan Claude Code
+
+Gunakan terminal lokal milik pengguna setelah mengganti domain contoh:
+
+```bash
+# Codex: tambahkan server, lalu login OAuth
+codex mcp add mso --url https://mso.example.com/mcp
+codex mcp login mso
+
+# Claude Code: tambahkan server dan periksa konfigurasinya
+claude mcp add --transport http mso https://mso.example.com/mcp
+claude mcp get mso
+```
+
+Di Claude Code, buka `/mcp` untuk menyelesaikan OAuth. Status dari `get` belum membuktikan
+izin setiap tool; tetap uji satu operasi read untuk membuktikan akses. Untuk Cursor, Gemini CLI,
+VS Code, atau klien lain, pilih klien tersebut di **Connect an app** agar mendapat konfigurasi
+sesuai instalasi. Jangan menaruh bearer/password di config bersama atau argumen shell.
+
+## 4. Mulai dengan tugas nyata
+
+Ganti `example-project` dengan nama/ID yang benar-benar dikembalikan MSO.
+
+| Tujuan | Contoh prompt |
+|---|---|
+| Status server | `@MSO cek CPU, RAM, disk, dan service yang bermasalah. Jangan ubah apa pun.` |
+| Pilih proyek | `@MSO tampilkan proyek yang tersedia agar saya bisa memilih target.` |
+| Baca dokumentasi | `@MSO baca README proyek example-project dan ringkas cara menjalankannya.` |
+| Ubah dokumentasi | `@MSO tambahkan panduan MCP ke example-project. Periksa aturan repo, jaga perubahan sesi lain, lalu validasi tautan.` |
+| Diagnosis akses | `@MSO periksa scope, tool yang tersedia, dan error sebenarnya. Jangan ubah credential atau izin untuk menutupi error.` |
+
+Sebutkan hasil yang diinginkan, proyek, batas perubahan, dan cara verifikasi.
+Scope `write` tidak menjamin shell tersedia; menjalankan shell/test melalui `exec_run`
+atau memanggil MCP proyek memerlukan `exec`. Prompt tidak bisa menaikkan scope token.
+
+## 5. Urutan tool untuk agent
+
+Untuk satu pembacaan sederhana, gunakan tool read yang sesuai. Untuk tugas multi-langkah:
+
+```text
+workflow_start (sekali) → inspeksi target → perubahan yang diizinkan
+→ verifikasi hasil → workflow_finish
+```
+
+`workflow_start` sudah mencari skill/konteks yang relevan; jangan mengulang `skills_search`
+sebelumnya untuk tugas sama. Contoh argumen bootstrap:
+
+```json
+{
+ "intent": "Periksa dokumentasi MCP proyek example-project tanpa mengubah file",
+ "project": "example-project",
+ "constraints": "Read-only; jangan restart service atau membuka credential"
+}
+```
+
+Simpan ID workflow dari respons. **Kirim ID persis itu sebagai `workflow_id` pada setiap
+operasi berikutnya**, bukan ID sesi/job atau ID workflow percakapan lain. Contoh `project_get`:
+
+```json
+{
+ "project": "example-project",
+ "workflow_id": "<workflow-id>"
+}
+```
+
+Periksa hasil sesuai tugas: file/diff untuk perubahan dokumen, test/build untuk kode,
+dan health/version untuk deployment. `workflow_finish` menerima `workflow_id`, `summary`,
+`success`, serta `evidence` terstruktur. Gunakan `success: true` hanya setelah hasil terbukti;
+catat kegagalan/risiko dengan jujur, atau gunakan `workflow_cancel` untuk pekerjaan yang dibatalkan.
+
+Jangan salin daftar atau jumlah tool secara manual ke instruksi. Gunakan
+[katalog otomatis](./generated/MCP-CATALOG.md) untuk referensi dan `tools/list` terautentikasi
+untuk izin aktual. `GET /mcp` menunjukkan identitas versi/hash deployment, bukan bukti token berfungsi.
+
+## 6. Pakai MCP milik proyek melalui MSO
+
+Koneksi masuk ke MSO tidak otomatis mengotorisasi akses ke layanan lain.
+Di **Integrations → Add MCP**, simpan endpoint HTTPS dan credential downstream lewat form privat;
+pilih pemilik credential serta koneksi yang tepat. Jangan mengirim token lewat chat.
+Registry plugin saja tidak cukup. [Kontrak koneksi privat](./PROJECT-MCP-CONNECTIONS.md).
+
+```text
+projects_list → pilih proyek persis
+→ project_capabilities(project) → pilih alias server dari hasil
+→ project_mcp_tools(project, server) → baca schema tool
+→ project_mcp_call(project, server, tool, arguments)
+```
+
+Ini urutan konseptual, bukan JSON siap kirim; sertakan `workflow_id` untuk setiap langkah
+bila sedang dalam workflow. Ikuti `nextCursor` dengan parameter `cursor` sampai habis.
+Discovery/call MCP proyek memerlukan `exec`; layanan tujuan tetap memeriksa izinnya sendiri.
+Jangan menebak nama tool/argumen, memakai token MSO sebagai token downstream, atau memindahkan
+credential lintas pemilik. Tool proyek tetap dinamis, bukan tambahan nama global di MSO.
+
+## 7. Troubleshooting dan pemeliharaan
+
+| Gejala | Pemeriksaan dan langkah berikutnya |
+|---|---|
+| `/mcp` atau discovery 404 | Pastikan domain/path benar, MCP aktif di proses berjalan, dan bukan demo. Cek `mso doctor`. |
+| Login OAuth gagal | Periksa HTTPS, perangkat Owner, redirect, serta kecocokan origin/resource. Jangan matikan autentikasi. |
+| 401 / expired token | Ulangi OAuth/reconnect. Jangan menyalin token dari log atau koneksi pengguna lain. |
+| 403 / scope denied | Periksa error, scope token, ceiling server, dan penolakan Origin/path. Jangan otomatis menaikkan ke exec. |
+| Tools kosong/hilang | Pastikan app aktif; cek scope, katalog live, dan scan/refresh setelah update. Uji chat baru untuk snapshot baru. |
+| `unknown tool` | Bedakan tool global dari tool proyek; lakukan discovery dan gunakan nama/schema terbaru. |
+| GET SSE menghasilkan 405 | MSO tidak menyediakan listener SSE. Gunakan klien Streamable HTTP, bukan endpoint SSE lama. |
+| MCP proyek belum terhubung | Periksa alias, endpoint persis, pemilik koneksi, token downstream, serta kebutuhan exec. |
+| Timeout / hasil terpotong | Pecah tugas, batasi output, dan ikuti pagination. Jangan mengulangi mutation sebelum memeriksa hasil sebelumnya. |
+| Workflow/job tidak ditemukan | Pastikan ID persis dan sesi/principal pemanggil benar. Jangan meminjam ID percakapan lain. |
+
+Sesudah update tool/schema, bandingkan versi/hash pada **Tools & updates**, refresh di klien,
+dan ulangi operasi read. Penanda refresh di MSO hanya pengingat lokal browser, bukan
+konfirmasi bahwa ChatGPT berhasil memindai ulang. Jumlah tool bisa berbeda menurut scope/profil.
+Putuskan akses yang tidak dipakai melalui **Connected apps** atau `mso mcp revoke <id>`;
+`mso mcp list` hanya menampilkan metadata. Service token khusus automation mempunyai
+allowlist terbatas, bukan pengganti umum OAuth: lihat [MCP reference](./MCP.md).
+
+## Referensi dan batas bukti
+
+[Dokumentasi OpenAI Developer Mode](https://developers.openai.com/api/docs/guides/developer-mode),
+[Codex MCP](https://developers.openai.com/codex/mcp), dan
+[Claude Code MCP](https://code.claude.com/docs/en/mcp) ditinjau 2026-09-13.
+Menu/dukungan klien bisa berubah; kode MSO dan descriptor live menjadi otoritas perilaku server.
+Panduan ini bukan klaim bahwa setiap klien, akun, atau koneksi downstream sudah diuji end-to-end.
diff --git a/docs/MCP.md b/docs/MCP.md
index d53568d8..7f290f04 100644
--- a/docs/MCP.md
+++ b/docs/MCP.md
@@ -1,5 +1,8 @@
# MCP — drive this VPS from ChatGPT, Claude.ai or Cursor
+> **First connection?** Start with [How to use MSO MCP — Bahasa Indonesia](./MCP-HOW-TO.md)
+> for setup, example prompts, workflow usage, and troubleshooting.
+
> **Current deep reference.** For ChatGPT specifically, use
> [`CHATGPT-PLUGIN.md`](./CHATGPT-PLUGIN.md) for current custom-MCP-app terminology,
> setup values and diagrams. This file owns protocol, tool, discovery, workflow and
@@ -21,7 +24,9 @@ demo mode also forces MCP off. Existing installs keep their current `.env.local`
## Settings navigation
-Settings → MCP opens a task index: **Connect an app**, **Connected apps**, **Recent activity**, **Tools & updates**, and **Connection details**. Setup first asks for the client and shows only that client's steps. Use **MCP overview** to return; technical OAuth/tunnel fields live under Connection details. Connected apps separates active access from expired/revoked history and confirms disconnection. Tools & updates stores only a browser-local refresh reminder, never a verified client-health claim.
+Settings → MCP separates **Access MSO** (external clients → MSO), **MSO Access** (MSO → external services / plugin declarations), and **Sessions** (activity and handover). SI-Coder is an optional plugin, not a prerequisite. Registry declarations do not install code or configure credentials.
+
+Access MSO opens a task index: **Connect an app**, **Connected apps**, **Recent activity**, **Tools & updates**, and **Connection details**. Setup first asks for the client and shows only that client's steps. Use **MCP overview** to return; technical OAuth/tunnel fields live under Connection details. Connected apps separates active access from expired/revoked history and confirms disconnection. Tools & updates stores only a browser-local refresh reminder, never a verified client-health claim.
Anonymous visitors see an Owner sign-in entry, not private API requests or an endless loading state. Failed settings/activity loads expose a retry action; activity failures never become an empty-success state. The public `/settings?section=mcp` deep link returns sign-in users to MCP.
diff --git a/docs/PROGRESS.md b/docs/PROGRESS.md
index c4bad964..940f22bd 100644
--- a/docs/PROGRESS.md
+++ b/docs/PROGRESS.md
@@ -1,3 +1,19 @@
+## 2026-09-13 — README MCP entry point and practical how-to
+
+Before: the product README linked general docs, while MCP onboarding was spread across
+long references and the ChatGPT refresh sequence still named an obsolete tool count.
+After: the README has a direct Use MCP entry point and explains inbound/outbound access;
+a Bahasa Indonesia how-to covers owner/HTTPS setup, least-privilege OAuth, client commands,
+first prompts, exact workflow correlation, dynamic project MCP discovery and troubleshooting.
+SI-Coder remains optional; registry declarations are explicitly not activation or credentials.
+Current references/index link to the guide, and snapshot verification uses the generated
+catalog rather than another hand-maintained count. The existing Page guidance now distinguishes
+reviewed exact-origin embeds from arbitrary URLs. No MCP schema, permission, or runtime code changed.
+Validation: documentation/catalog/comparison checks, both JSON examples, shell syntax and
+14 targeted client-guide/direction/integration-contract tests pass. Full repository gates remain
+required by the normal ship path. External-client snippets are source-checked guidance, not
+a claim that new OAuth accounts were connected end-to-end.
+
## 2026-09-12 — Native scrollbars follow the active theme
Direct inspection in the owner browser found a white native Settings scrollbar inside
diff --git a/docs/README.md b/docs/README.md
index b36f7eed..2cf23411 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -35,6 +35,7 @@ evidence and review freshness. The repository quality gate runs both automatical
| [`INTEGRATIONS.md`](./INTEGRATIONS.md) | Native temporary credential forms, direct HTTPS secret submission, CLI and ChatGPT Page |
| [`PROJECT-MCP-CONNECTIONS.md`](./PROJECT-MCP-CONNECTIONS.md) | Named private connections, endpoint binding and identity for modular project MCPs |
| [`AUTOMATION-FLOWS.md`](./AUTOMATION-FLOWS.md) | Versioned project API/MCP flows, CLI, sessions, Add MCP, assets and limits |
+| [`MCP-HOW-TO.md`](./MCP-HOW-TO.md) | Bahasa Indonesia onboarding: client connection, prompts, workflow, project MCP and troubleshooting |
| [`MCP.md`](./MCP.md) | MCP/OAuth internals and full external-tool security model |
| [`A2A.md`](./A2A.md) | A2A v1 peer discovery, delegation/task lifecycle, CLI/MCP surface and trust boundary |
| [`LOCAL-AGENTS.md`](./LOCAL-AGENTS.md) | Native same-host session presence, identity, mailbox delivery, TUI/tools/API and isolation |