MCP server
This topic provides an overview of the OpenText Core Software Delivery Platform MCP Server.
Overview
The OpenText Core Software Delivery Platform MCP Server exposes OpenText Core Software Delivery Platform 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
Gradual exposure: The OpenText Core Software Delivery Platform MCP capabilities are being exposed gradually throughout 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.
Connect to the MCP server
Users connect to the MCP server by declaring the MCP in their AI client's MCP JSON file.
Authentication: Connection to the MCP server can be authenticated either through the standard user login (OAuth) or using an API access token. To create an API access token, see API access.
To connect an AI client to the MCP server:
-
See Connect an AI client.
Protocol details
-
The MCP server runs embedded inside OpenText Core Software Delivery Platform 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

