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 standard AI assistants, such as Claude Desktop and GitHub Copilot, and custom harnesses and agents 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, and add comments
  • Inspect field metadata for any entity type

All actions performed through the MCP respect the workspace permissions of the logged in user or API key.

Disclaimer

The MCP server and its licensing terms are subject to change in future 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.
  • add_comment: Adds a comment to an entity.

For full tool specifications, see Build custom integrations.

Set up and connect

Set up MCP access and connect supported AI clients.

Prerequisites

A shared-space administrator configures MCP access:

  1. For OAuth authentication, enable OAUTH2_ADMIN_CONSENT_GRANTED for the shared space. For details, see Configuration parameters.

  2. For API key authentication, create an API access bearer token in the target space and provide it to the client configuration. For details, see API access.

  3. In Permissions > General System Actions, grant MCP permissions to selected roles:

    • Access MCP Server: Grants MCP access to assigned users.

    • Use MCP Write operations: Grants access to the MCP write tools for assigned users when Access MCP Server is also enabled.

    For details, see Roles and permissions.

Connect AI clients

Users add the MCP server to their AI clients. For details, see Connect AI client to MCP server.

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