OutcomeCI MCP Server

MCP serverAI & models

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

Use OutcomeCI MCP Server in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add OutcomeCI MCP Server and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use OutcomeCI MCP Server

Details

Available today. Use it from your connected AI after setup.

Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

OutcomeCI MCP ServerStart free

Install OutcomeCI MCP Server

The server’s own address, for the clients that take one directly. Or connect ahel once and every client you use reads it from one address, with the account kept on ahel rather than in each client’s config.

  • Claude Code

    claude mcp add --transport http --scope user outcomeci-mcp-server 'https://api.outcomeci.com/v1/mcp'

    Run it once in your project, then open /mcp to approve any sign-in the server asks for.

  • Claude Desktop

    https://api.outcomeci.com/v1/mcp

    Add a custom connector in Settings, paste this address, and approve the sign-in.

  • Cursor

    cursor://anysphere.cursor-deeplink/mcp/install?name=outcomeci-mcp-server&config=eyJ1cmwiOiJodHRwczovL2FwaS5vdXRjb21lY2kuY29tL3YxL21jcCJ9

    Open the link and Cursor adds the server at that address.

  • ChatGPT

    https://api.outcomeci.com/v1/mcp

    In Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.

  • Codex

    codex mcp add outcomeci-mcp-server --url 'https://api.outcomeci.com/v1/mcp'

    Run it once, then sign in with codex mcp login outcomeci-mcp-server if the server asks for an account.

From the project's README

As published by outcomeci/mcp-server in README.md.

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:

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.

Signals

GitHub stars
1
Last commit
Oct 2026
Advanced
Delivery
OutcomeCI MCP server → your ahel connector (mcp.ahel.ai) → your AI.
Item type
mcp-server
Key
io-github-outcomeci-mcp-server
Source
github.com/outcomeci/mcp-server
Hosted endpoint
https://api.outcomeci.com/v1/mcp