Connect your agent
Use your agent to help create and manage OutcomeCI workflows through MCP (Model Context Protocol). Connect it to your workspace, describe the work, and build the workflow together.
What you need
- An OutcomeCI account with access to a workspace.
- An agent or assistant that supports remote HTTP MCP servers and browser-based OAuth authorization.
This connection lets your assistant configure OutcomeCI. The agent that executes a workflow is selected separately in the workflow's reasoning configuration.
Add the MCP server
Open your agent's MCP server or connector settings and add a remote server:
| Setting | Value |
|---|---|
| Name | OutcomeCI |
| Server URL | https://api.outcomeci.com/v1/mcp |
| Connection | HTTP |
| Authentication | OAuth |
Settings names vary between clients. Choose a remote HTTP connection rather than a local command. Your client must support OAuth discovery and client registration.
Official agent setup guides
Use your client's guide for its setup and authentication steps, with the OutcomeCI server URL above:
- Claude Code MCP setup guide: add a remote HTTP server and authenticate it from Claude Code.
- Codex MCP setup guide: configure a remote MCP server and complete OAuth authorization.
- OpenCode MCP setup guide: connect a remote MCP server and sign in with OAuth.
Authorize your workspace
Start the connection from your agent. It opens OutcomeCI in your browser.
- Sign in to OutcomeCI if prompted.
- Select the workspace you want the agent to help configure.
- Review the requested access.
- Select Allow access and return to your agent.
The authorization applies to the selected workspace. If no workspace appears, create one in OutcomeCI or ask a workspace owner for access, then reconnect.
Build a workflow together
Start with a request like:
Help me create an OutcomeCI workflow that takes a feature request from Slack, discusses a plan with the requester, waits for their approval, and opens a pull request in the agreed repository. Show me the workflow before publishing it.
Your connected agent can discover the workflow format, inspect existing workflows, and help create or update them within the access you approved.
When a tool needs credentials, use the browser-based credential form supplied by OutcomeCI. Credentials go into your Vault; their values are not shared with the assistant.
If the connection does not complete
Confirm the full URL includes /v1/mcp, and check that your client supports
remote HTTP MCP with OAuth discovery and registration. A client that only
supports local command-based servers cannot connect directly to this endpoint.
If you canceled authorization or chose the wrong workspace, start the connection again from your agent.
For the workflow building blocks, see Write a workflow. To build and test from your terminal instead, follow the Quickstart.