Changelog
Back to All
Improved

MCP Server v0.0.1-beta.15

about 2 months ago by ReadMe API

Explicit Account-Wide Access

Eligible users can authorize Entire account, including future projects during OAuth consent. This enables account-wide tools, including project creation, subject to backend roles, permissions, plan limits and the role approved at consent.

Selecting all existing projects remains a selected-project grant, not access to future projects. Existing grants are not automatically expanded. Reconnect only to deliberately approve broader access. Local API-key/HMAC permissions are unchanged.

Approval Governance

  • Approval requirements return actionable request information. Preserved request IDs let agents inspect pending requests instead of submitting duplicates.
  • Approval actions require explicit, target-bound confirmation. MCP never automatically approves or retries an approved action.
  • Account-wide approval settings require account-wide hosted consent. Write profiles remain subject to backend permissions and independent-review requirements.

Project Management And Reliability

  • Project creation is available only to eligible hosted grants and is checked against the exact account at execution. New projects are discoverable with an existing entire-account grant.
  • Project deletion requires an explicit request followed by a second confirmation naming the exact numeric resource. Read-only profiles do not expose deletion.
  • Grant-aware catalogs recover after transient scope-resolution failures and notify compatible clients when the catalog changes.
  • Refreshed knowledge search preserves existing document-ID compatibility and local/hosted semantic retrieval.
  • Improved validation covers newly available project lifecycle operations.

Notifications Deferred

Notification settings and history are disabled by default pending backend rollout. Disabled tools are absent from the catalog and reject stale calls. This release does not change notification settings or delivery in the Convert application.

The local package remains stdio; hosted-only runtime code is not its npm entrypoint. Existing local and hosted clients continue working without configuring notifications.