Capture

Capture: three surfaces and MCP

Desktop, Chrome, and phone remain the built-in surfaces and all write back to the same local vault. Third-party sources are not embedded — connect them with MCP capture. This page only documents paths that have shipped.

Bring any source over MCP

Mycel does not embed Feishu, web, or chat integrations. Any MCP client can call capture and drop content into Dropt/Inbox/. Args are {content, title?, source, sourceUrl?, intent?}; the tool returns {created, cid, relativePath}. The same payload is idempotent (created: false). Write tools are Pro-gated and leave an Audit trail.

Contract, minimal call, the Feishu zero-secret example, and troubleshooting: Bring your own capture source.

Desktop capture

Mycel includes a Dropt capture window and pairing panel. Captures land in the local vault — you do not need to sync notes to the cloud first.

If you see a phone-pairing entry in the menu or Settings, you can generate a QR code for the local capture page; the phone then posts text to the desktop bridge.

Chrome extension

  1. Use a build already published to the store. The unpacked extension is not publicly distributed; email silicoville@gmail.com to request it.
  2. The extension can save the current page URL, selected text, and handwritten notes. When the local bridge is unavailable, items go into an offline outbox.
  3. The popup shows connection status; if it fails, confirm the Mycel desktop app is running.

Local phone page

Phones can submit through the local capture page exposed by the desktop app. The Android PWA declares a share_target, so system-shared text or links can open the Mycel capture page.

The iOS share path uses a Shortcut. Shipping the iCloud link and finishing device smoke tests are still open. Configure the Shortcut yourself before relying on it; email silicoville@gmail.com for the current notes.

Relay mode

When phone and computer are not on the same LAN, Dropt relay can ferry the traffic. The relay only stores and returns encrypted payloads — it never decrypts note content. After a successful desktop drain, the queue item is deleted from the relay.

To run your own relay, see Self-host relay.

Offline and failures

  • When the Chrome extension cannot reach the local bridge, it queues in an outbox.
  • The local phone page caches itself and keeps pending sends when the browser supports a service worker.
  • If a capture lands correctly, Today can reflect it in the recent growth curve and activity metrics for that day.
  • If a capture never appears in the vault, check that the desktop app is running, then inspect relay or local bridge status from Today or the automation status surfaces.