Changelog
Back to All
Improved

MCP Server v0.0.1-beta.16

about 1 month ago by ReadMe API

This release improves protocol compatibility, catalog refresh, documentation search and connection handling while preserving existing Convert permissions and authentication.

Protocol And Catalogs

  • Hosted MCP supports 2026-07-28 alongside the existing protocol adapter. Unsupported versions are not silently rewritten.
  • Tools, prompts, resources, schemas, permission checks and destructive-action confirmations remain consistent across supported protocols.
  • Compatible modern clients can subscribe to catalog-change notifications within the same authorization grant. Notifications are deduplicated and revalidate authorization; explicit refresh remains the fallback.
  • Client support determines whether notifications trigger automatic refresh or resubscription.

Search And Reliability

  • Improved hosted documentation-search efficiency while preserving semantic retrieval, support-first ranking, document-ID compatibility and direct fetch.
  • Safer session recovery preserves authentication boundaries and never automatically replays writes.
  • Cancellation propagates through API requests and documentation search. When an underlying model operation cannot be interrupted, its result is discarded instead of starting further work.

Compatibility And Limits

No customer configuration change or new OAuth consent is required. Hosted clients retain their endpoint, grants and account/project scopes. The npm package remains a local stdio server using the same API-key/HMAC setup.

Local users configured with npx -y @convertcom/mcp-server@latest receive the published version on their next launch, subject to client caching; already-running processes need a restart.

Notification settings and history remain disabled pending backend support. Explicit account-wide consent, approval requirements and two-step deletion confirmation remain unchanged.

Catalog refresh does not guarantee interruption-free transport handover. An existing legacy session may encounter a documentation-search timeout during an upgrade; subsequent sessions can recover without OAuth reauthorization.