Release v2.0.2095 · Mcpgate-de/mcpgate

Imported connectors gain the operations that were silently dropped.
Imports now report which operations produced no action.
The confirmation prompt now asks about blast radius, not the HTTP verb.
Risk categories now recognise imported action names.
A risk category now says whether it prompts or disables.
Confirmation now tracks reach, not recoverability.
One decision for what a path addresses.
Confirmation now explains itself, and reach is read from the API's own structure.
Shared automations now advertise the arguments they accept.
A shared automation's approval now remembers what it accepted.
Pipedrive notes are now readable.
Form-encoded request bodies.
Connection tiles can now verify the upstream is actually reachable.

A parameter a connector cannot apply is refused instead of ignored.
Confirmation gate covers vendor resource:verb endpoints.
A destroying operation is recognised when the path names it, not only when the method does.
The advertised automation arguments stay current.
Pipedrive deals, contacts and notes accept quoted ids.
Four auth error paths now name the failure.
Auto-merge intent is never silently lost.
Confirmation gate now covers irreversible POST operations.
Names the failure in two more connector error paths.
A field the upstream really has is no longer shadowed by the caller's identity.
An OpenAPI import now says what it will not be able to send.
Guest invites now cover per-user-credential services.
Concurrent admin visibility changes no longer overwrite each other, and a freshly connected hidden service says so.
Outbound request errors now name the failure.
Grafana log search now applies every search term.
Actions no longer ask for metadata the service does not want.
Starting an MCP session no longer scales with the size of the install.
Refreshing a token from the connections page uses the same coordination as everywhere else.

Docker: docker pull mcpgate/mcpgate:2.0.2095

Navigation Menu