MCP server

This topic provides an overview of the OpenText Software Delivery Management MCP Server.

Overview

The OpenText Software Delivery Management MCP Server exposes OpenText Software Delivery Management data and actions through the Model Context Protocol (MCP).

The MCP server supports both standard AI clients, such as Claude Desktop and GitHub Copilot, and custom integrations built on MCP.

Connected clients and integrations can do the following:

  • Browse all available entity types
  • Query, filter, and search entities
  • Create and update entities
  • Inspect field metadata for any entity type

MCP support:

  • MCP is disabled by default. To enable MCP, contact support.

  • The MCP capabilities are being exposed gradually over the upcoming releases.

Supported tools

The MCP server exposes the following tools:

  • get_entity_types: Lists entity types available in the workspace.
  • get_entity_field_metadata: Shows fields and field types for an entity type.
  • get_filter_metadata: Returns filter syntax and operators.
  • get_entities: Lists entities with optional filtering, search, sorting, and pagination.
  • get_entity: Retrieves one entity by ID.
  • create_entity: Creates a new entity.
  • update_entity: Updates selected fields on an existing entity.

For full tool specifications, see Build custom integrations.

Set up and connect

Using the MCP server includes the following steps:

  1. The OpenText Software Delivery Management admin enables AI tool authentication with API keys or OAuth 2.1. See Enable MCP and register clients.

  2. Users add the MCP server to their AI clients. See Connect an AI client.

  3. For common connection issues, see Troubleshooting.

You can create custom integrations using the MCP server. For details, see Build custom integrations.

Protocol details

  • The MCP server runs embedded inside OpenText Software Delivery Management and is reachable over HTTPS at the path /mcp. No local process or proxy is required.

  • Transport: stateless HTTP (POST for tool calls, GET for endpoint discovery)
  • No Server-Sent Events (SSE) — every request is self-contained
  • All communication uses JSON-RPC 2.0