Integrations
What a workflow can reach.
A workflow runs steps in the family products today. Connectors for the outside tools your team already uses are planned, and each one below shows its state.
The family
Our products.
| Product | What it does in a workflow | How a step reaches it | State |
|---|---|---|---|
| RepoOps | Production errors, the agent session behind a change, recovery and the shared brain. | https://mcp.repoops.ai/mcp | Built |
| PromptCompute | Approvals: the exact action goes to a person before it runs, and each decision is signed. Also holds agent identity and PromptReports ID. | https://mcp.promptcompute.ai/mcp | Built |
| ContextFile | Versioned context for agents: which version each session read, what changed since, and quarantine for what it reads from others. | https://mcp.contextfile.ai/mcp | Built |
| AI Source of Truth | A public record you can check later: provenance, accuracy figures and corrections, as they stood on any past date. | https://aisourceoftruth.com/v1/family/facts | API |
| Sales as Code | Forecasts and outreach that score themselves. Discounts and commitments wait for a person. | None known yet | To confirm |
| CommitOps | Every promise to a customer and the work behind it, and whether it can land by a date. | https://commitops.ai/api/mcp | Built |
Outside products
The tools you already use.
| Product | How it will connect | Phase | State |
|---|---|---|---|
| GitHub | Remote MCP | First | Planned |
| Slack | Remote MCP, or the Slack Web API | First | Planned |
| Linear | Remote MCP | First | Planned |
| Any webhook | A trigger: a signed call from any service starts a run | First | Planned |
| Any HTTP API | Any HTTP endpoint | First | Planned |
| Jira and Confluence | Remote MCP | Second | Planned |
| Notion | Remote MCP | Second | Planned |
| Sentry | Remote MCP | Second | Planned |
| HubSpot | Remote MCP | Second | Planned |
| Stripe | Remote MCP | Second | Planned |
| Salesforce | API actions | Second | Planned |
| Zendesk | API actions | Second | Planned |
| Datadog | API actions | Second | Planned |
| Google Workspace | API actions | Second | Planned |
How
Three ways to connect.
| Remote MCP | The product runs an MCP server, and the runner calls its tools. Every family product with an MCP server connects this way. |
| API actions | Chosen operations from a vendor's OpenAPI document, each named by its operationId. Never a whole generated catalog. |
| Any HTTP endpoint | A call to a URL you name, with a secret you store, through one proxy that refuses private addresses and limits the size and time of each answer. |
Each outside connector reads Planned until it ships. Read Connectors in the docs for how a connector works, and tell us which tool you need next.