dsh-lazy-mcp

LIMITATIONS

Known limitations

- **Text-only results.** Raw MCP blocks are summarized: text passes through, images/audio/resources become explicit `[image omitted: …]` markers. The official bridge additionally performs durable image projection through the attachment service; that is deliberately not reimplemented here. - **Binary resources are reported, not delivered.** A `blob` body becomes a size notice; the bytes stay with the server. Programmatic callers would need the official bridge. - **No re-notification sync.** If a connected server changes its tool list mid-session, the cached list is refreshed on the next connect rather than by a `list_changed` subscription. Resource lists are never cached, so they are always read live. - **No OAuth.** Authenticated servers use static `headers`. - **No prompt templates, resource subscriptions, or task-based execution.** - **No `directTools`.** Every MCP tool is reached through `mcp_call`; none is registered as a first-class tool with its own schema in the tool catalog. - **No `includeTools` / `excludeTools` filtering**, and no `searchKeywords`. - **`mcp_servers` reports cached state** and never probes a dormant server. - **UI status labels are Chinese.** Behaviour is unaffected; a localization PR is welcome.