OutcomeCI

io.github.outcomeciv1.0.0Updated Oct 5, 2026

Create, validate, and manage agent-powered workflows with OutcomeCI.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & MonitoringProductivity & Workflow

Overview

AI-generated overview

Lets an assistant create, validate, and manage OutcomeCI agent-powered workflows, including runs, triggers, and credential deposits.

What it does
Connects an assistant to a hosted OutcomeCI workspace over remote Streamable HTTP. Tools list workspaces, workflows, and agent connections; read workflow definitions and the outcome.yml schema; inspect connector schemas and integration setup guides; validate a workflow package without saving it; create workflows and upload immutable versions; configure email or webhook triggers; create credential deposit links and check their status; list vault entry metadata; and list, inspect, or cancel workflow runs.
When to use it
Use it when a team already runs workflows on OutcomeCI and wants an assistant to draft, validate, version, or troubleshoot them from chat. It suits inspecting recent runs and logs, or wiring a request from one tool into an action in another. It is not useful without an OutcomeCI account and workspace.
Requirements
A remote MCP client that supports Streamable HTTP and OAuth. No local install or shared API key; each person signs in to OutcomeCI through the browser and authorizes a workspace. Available tools depend on granted permissions, and configuring a workflow may also need connectors, credentials, and an agent connection.
Before you install
Authorize only the workspace and permissions you intend to grant, and use client approval controls for saving workflows, configuring triggers, or cancelling runs. Never paste credentials into chat; use the secure deposit link instead. Treat deposit links, inbound webhook URLs, and run logs as sensitive. Usage is billed under OutcomeCI pricing, so connecting an assistant does not make workflow execution free.

Installation

In SourceWeft

  1. Open OutcomeCI in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "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:

text
https://api.outcomeci.com/v1/mcp
  • 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.

ToolWhat it does
list_workspacesShow the workspace authorized for the connection.
list_workflowsList workflows and their latest metadata.
get_workflowRead a workflow's latest definition and support files.
get_workflow_schemaGet the current outcome.yml contract and an example.
get_connector_schemaInspect a connector's operations and credential requirements.
get_integration_setup_guideGet setup guidance for an integration.
validate_workflowValidate a complete workflow package without saving it.
create_workflowCreate a workflow and its first version.
upload_workflow_versionSave a new immutable version with checks against concurrent changes.
configure_workflow_triggerConfigure supported email or webhook triggers.
create_credential_depositCreate a secure UI link for depositing a credential.
get_credential_deposit_statusCheck a deposit's status without retrieving its secret.
list_vault_entriesInspect credential metadata and grants, not secret values.
list_agent_connectionsList connected agents' metadata.
list_workflow_runsList recent runs for a workflow.
get_workflow_run_logsRead paginated run logs.
cancel_workflow_runRequest cancellation of an active run.

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.

Source: README.md at commit f644b11

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestOct 5, 2026