Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Model Context Protocol server for OpenText Software Delivery Platform.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://almoctane-{region}.saas.microfocus.com/mcp地址中有只有你知道的 {…} 部分(例如你的账户),请复制后自行填写。
在终端中运行这条命令
claude mcp add --transport http sdp-remote 'https://almoctane-{region}.saas.microfocus.com/mcp'地址中有只有你知道的 {…} 部分(例如你的账户),请复制后自行填写。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"sdp-remote": {
"url": "https://almoctane-{region}.saas.microfocus.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
地址中有只有你知道的 {…} 部分(例如你的账户),请复制后自行填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"sdp-remote": {
"type": "http",
"url": "https://almoctane-{region}.saas.microfocus.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://almoctane-{region}.saas.microfocus.com/mcp地址中有只有你知道的 {…} 部分(例如你的账户),请复制后自行填写。
菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 opentext.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
这个地址需要填入你自己的账户信息,所以我们无法替你检查
这个地址需要填入你自己的账户信息,所以我们无法替你检查
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于23天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, AvaHR
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Read hiring data and create inactive assessment and questionnaire drafts for human review.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
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 deployment | Also known as | Guide |
|---|---|---|
| Core Software Delivery Platform | OpenText ValueEdge | [README-Core-Software-Delivery-Platform.md](README-Core-Software-Delivery-Platform.md) |
| Software Delivery Management | OpenText ALM Octane | [README-Software-Delivery-Management.md](README-Software-Delivery-Management.md) |
The Model Context Protocol server runs embedded inside the product and is reachable over HTTPS at the /mcp path.
| Protocol | Stateless HTTP — POST for tool calls, GET for endpoint discovery; JSON-RPC 2.0 |
| Authentication | OAuth 2.1 (interactive browser flow) · API access key (headless or service use) |
| Hosting | Embedded in the product — on-premise and cloud |
| Permissions | Every action is scoped to the authenticated user's workspace access |
Connect your AI client to your workspace and interact with delivery data without leaving your IDE:
| Capability | Example 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?"* |
Both products expose the same tool set:
| Tool | Description |
|---|---|
get_entity_types | Lists entity types available in the workspace |
get_filter_metadata | Returns filter syntax and supported operators |
get_entity_field_metadata | Shows fields and field types for an entity type |
get_entities | Lists entities with optional filtering, search, sorting, and pagination |
get_entity | Retrieves a single entity by identifier |
create_entity | Creates a new entity |
update_entity | Updates selected fields on an existing entity |
These apply equally to both products:
The detailed, link-accurate instructions live in the product guides. At a high level, the sequence is identical for both products:
OAUTH_AUTHORIZATION_SERVER_CLIENTS site parameter, including the redirect addresses for each client.Continue in [README-Core-Software-Delivery-Platform.md](README-Core-Software-Delivery-Platform.md) for OpenText ValueEdge, or [README-Software-Delivery-Management.md](README-Software-Delivery-Management.md) for OpenText ALM Octane.
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.
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.