Back to Browse

OpenText Model Context Protocol Server MCP Server

Developer ToolsLow Risk9.9MCP RegistryRemote
Free

Server data from the Official MCP Registry

Model Context Protocol server for OpenText Software Delivery Platform.

About

Model Context Protocol server for OpenText Software Delivery Platform.

Remote endpoints: streamable-http: https://almoctane-{region}.saas.microfocus.com/mcp

Security Report

9.9
Low Risk9.9Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

Endpoint verified · Open access · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "com-opentext-sdp-remote-mcp": {
      "url": "https://almoctane-{region}.saas.microfocus.com/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

OpenText Model Context Protocol Server

OpenText Model Context Protocol compatible Authentication: OAuth 2.1 or access key Hosting: on-premise and cloud

The official Model Context Protocol server for OpenText delivery products — embedded directly inside the product, with no local proxy or additional process required. Once enabled, your AI tools get real-time read and write access to your backlog, work items, and delivery data. Authentication uses OAuth 2.1 or API access keys, so every action respects the user's existing workspace permissions.


Choose your guide

This repository documents two products. They share the same protocol, the same tool set, and the same client configuration, but they are built on different documentation bases and release lines. Pick the guide that matches your deployment.

Your deploymentAlso known asGuide
Core Software Delivery PlatformOpenText ValueEdgeREADME-Core-Software-Delivery-Platform.md
Software Delivery ManagementOpenText ALM OctaneREADME-Software-Delivery-Management.md

Contents


What the server does

The Model Context Protocol server runs embedded inside the product and is reachable over HTTPS at the /mcp path.

ProtocolStateless HTTP — POST for tool calls, GET for endpoint discovery; JSON-RPC 2.0
AuthenticationOAuth 2.1 (interactive browser flow) · API access key (headless or service use)
HostingEmbedded in the product — on-premise and cloud
PermissionsEvery action is scoped to the authenticated user's workspace access

What you can do

Connect your AI client to your workspace and interact with delivery data without leaving your IDE:

CapabilityExample prompt
Search and filter"List all open defects assigned to me in the current sprint."
Find by keyword"Find all stories in the backlog that mention performance."
Create work items"Create five user stories from these meeting notes."
Update entities"Update the description of story #1042 with these acceptance criteria."
Explore metadata"What fields does a Feature entity have?"
Check status"What is the current status of epic #205?"

Supported tools

Both products expose the same tool set:

ToolDescription
get_entity_typesLists entity types available in the workspace
get_filter_metadataReturns filter syntax and supported operators
get_entity_field_metadataShows fields and field types for an entity type
get_entitiesLists entities with optional filtering, search, sorting, and pagination
get_entityRetrieves a single entity by identifier
create_entityCreates a new entity
update_entityUpdates selected fields on an existing entity

Shared prerequisites

These apply equally to both products:

  • An active product site, either on-premise or cloud
  • The Model Context Protocol feature enabled by your OpenText administrator
  • One of the supported AI clients: Visual Studio Code with GitHub Copilot, IntelliJ with GitHub Copilot, Claude Desktop, or Cursor
  • For OAuth 2.1: a modern browser to complete the sign-in flow
  • For an access key: an API access token generated in the target workspace
  • An Aviator AI license for each agent or user that connects
  • Each connection consumes a named user license, the same as any regular user accessing the workspace

Shared setup outline

The detailed, link-accurate instructions live in the product guides. At a high level, the sequence is identical for both products:

  1. Enable the feature. A site administrator submits a support ticket to have the Model Context Protocol enabled for the site or tenant.
  2. Choose an authentication method. OAuth 2.1 for interactive clients, or an access key for headless and service setups.
  3. Register your clients (OAuth 2.1 only) in the OAUTH_AUTHORIZATION_SERVER_CLIENTS site parameter, including the redirect addresses for each client.
  4. Configure your AI client with the server address and the chosen credentials.
  5. Verify the connection by listing the available tools in your client.

Continue in README-Core-Software-Delivery-Platform.md for OpenText ValueEdge, or README-Software-Delivery-Management.md for OpenText ALM Octane.


Security

All traffic is encrypted in transit over HTTPS using TLS 1.2 or later. Access is strictly bounded by the authenticated user's existing workspace permissions; the server cannot grant broader access than the user already has.

Caution: Avoid embedding access tokens as plain text in configuration files. Where the client supports it, use an environment variable or a client-managed input variable instead.

Use of the server is subject to the OpenText End User License Agreement, available on the OpenText agreements page, and to the applicable service description for your deployment.


Support and feedback


Disclaimer

The server performs actions in the product with the permissions of the authenticated user. Apply least privilege, review high-impact changes before confirming, and monitor audit logs for unusual activity.

Reviews

No reviews yet

Be the first to review this server!