Skip to content

endpoint_manage

← MCP reference
View in MCP reference →
TOOL endpoint_manage

Manage the names, types and registry entries of your devices and connected services.

Choose one operation: RENAME, SET_TYPE, SET_ENABLEMENT, MERGE_INTO, or DELETE. Use endpoint_query first and copy the full endpoint ID. Rename and type changes are durable across provider rediscovery. Disabled endpoints stay available for explicit metadata reads, but cannot receive messages; rediscovery preserves the disabled state. DELETE removes the registry entry, though a provider may rediscover it later. MERGE_INTO retains the source endpoint as disabled and moves supported references to the target; it does not create a source-ID alias, and the target's enablement remains in effect. Before MERGE_INTO or DELETE, identify the actual endpoint and explain the effect to the user; never assume two endpoints are duplicates because their names match. This tool changes registry metadata only and never performs physical control.

Required scope

endpoint:write

Input

Fields

enablementstring

New endpoint enablement; only for SET_ENABLEMENT.

Allowed values: ENABLED, DISABLED.

endpointIdstringRequired

Full endpoint ID from endpoint_query.

mergeIntostring

Full target endpoint ID; only for MERGE_INTO.

namestring

New endpoint name; only for RENAME.

operationstringRequired

Allowed values: RENAME, SET_TYPE, SET_ENABLEMENT, MERGE_INTO, DELETE.

typestring

New ontological endpoint type; only for SET_TYPE.

Result

Fields

endpointIdstringRequired
mergeIntostring
operationstringRequired
statusstringRequired

Allowed values: UPDATED, DELETED.

Errors

A failed call returns this error object as its result instead.

Fields

familystringRequired

The broad class of an error. The family decides the HTTP status of a REST error, so clients can handle every code of a family alike.

codestringRequired

The specific error, one of a closed set of Port OS codes. Every REST error body, MCP tool error, batch item error and discovery item error uses this enum; each code belongs to an `ErrorFamily` that decides its HTTP status. Provider-specific codes are never codes: they travel in `details.providerCode`. New failure kinds are added here, never as free strings.

messagestringRequired

Plain-language description of the failure and the suggested next action.

detailsErrorDetails

Optional typed context for an error. Fields are additive and only populated when the error can safely expose that context to API clients.

errorsarray<SynchronizationItemError>

Every rejected item when a request that is validated item by item and applied atomically fails, such as a discovery `SynchronizationRequest` whose routes, group routes or relationships are rejected. Omitted for single-item failures.