
OutcomeCI
io.github.outcomeciv1.0.0更新於 Oct 5, 2026
Create, validate, and manage agent-powered workflows with OutcomeCI.
概覽
讓助理建立、驗證與管理工作流,包括 OutcomeCI 的代理式工作流、執行紀錄、觸發條件與憑證存入。
- 功能
- 透過遠端 Streamable HTTP 將助理連線到代管的 OutcomeCI 工作區。工具可列出工作區、工作流與代理連線;讀取工作流定義與 outcome.yml 結構;檢視連接器結構與整合設定指南;在不儲存的情況下驗證工作流套件;建立工作流並上傳不可變版本;設定電子郵件或 webhook 觸發條件;建立憑證存入連結並查詢狀態;列出保存庫項目中介資料;以及列出、檢視或取消工作流執行。
- 適用情境
- 適合已在 OutcomeCI 上執行工作流的團隊,希望助理在對話中草擬、驗證、版本控管或排查工作流。也適合檢視近期執行與日誌,或把某個工具的請求接到另一個工具的動作上。沒有 OutcomeCI 帳號與工作區時並不實用。
- 執行需求
- 需要支援 Streamable HTTP 與 OAuth 的遠端 MCP 用戶端。不需本機安裝或共用 API 金鑰;每個人透過瀏覽器登入 OutcomeCI 並授權一個工作區。可用工具取決於所授予的權限,設定工作流可能還需要連接器、憑證與代理連線。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 OutcomeCI,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"mcp-server": {
"type": "http",
"url": "https://api.outcomeci.com/v1/mcp"
}
}
}README
OutcomeCI MCP Server
Connect your AI assistant to OutcomeCI to create, validate, and manage agent-powered workflows across the tools your team uses.
This is the public connection and documentation repository for OutcomeCI's hosted Model Context Protocol (MCP) server. It contains server metadata and client configuration—not the hosted backend or a self-hosted server distribution.
Connect
Add OutcomeCI as a remote MCP server in your client:
- Transport: Streamable HTTP
- Authentication: OAuth through your browser
- Access: Sign in to OutcomeCI and authorize a workspace
No local server installation or shared API key is required. Each person authorizes their own connection. Your client must support remote Streamable HTTP servers and OAuth.
Setup guides
For clients that accept this configuration format, see the example configuration. Other clients may use different field names; follow their remote-server setup instructions.
Try it
Ask your connected assistant:
List the workflows in my OutcomeCI workspace.
Read the workflow schema and help me create a workflow that turns a Slack request into a GitHub pull request. Validate it before saving.
Show the recent runs for my workflow and inspect the logs for the latest failure.
Available tools depend on the permissions granted to the connection. Configuring a workflow may also require connectors, credentials, and an agent connection.
Tools
The server exposes the following tools. Your client's live tools/list response is authoritative for the current schemas and authorized tool set.
Permissions and credentials
Authorize only the workspace and permissions you intend to give your assistant. Use your client's approval controls for changes such as saving workflows, configuring triggers, or cancelling runs.
Never paste credentials into chat. Use the secure deposit link when a workflow needs a secret. Treat deposit links, inbound webhook URLs, and run logs as potentially sensitive; do not include them in public issues.
Pricing
OutcomeCI Cloud usage is billed according to OutcomeCI pricing. Connecting an assistant does not make workflow execution free.
Documentation and feedback
For documentation problems or feature requests, open an issue. Include the client name and a sanitized description; never include tokens, secrets, or private workflow data.
Repository metadata
server.json describes the hosted endpoint using the MCP Registry server schema. Its version tracks this repository's metadata, not a pinned version of the hosted service. Including the manifest does not imply that a directory or registry has approved the listing.
License
This repository's documentation, metadata, and configuration examples are licensed under the MIT License. The hosted backend is not distributed in this repository.
來源:README.md,提交 f644b11
工具
0版本歷史
1- v1.0.0最新Oct 5, 2026


