PPromptReports

Connectors

A connector is how a workflow step reaches a product. Today the runner reaches the family products through their MCP servers. Connectors for the tools your team already uses are planned.

Each connector will list the product's actions and say whether each one reads, writes or deletes. Your PromptCompute policy decides which of those a person approves first. A connector will also name the events that can start a run.

Three ways to connect

WayHow it works
Remote MCPThe product runs an MCP server, and the runner calls its tools. Every family product with an MCP server connects this way.
API actionsChosen operations from a vendor's OpenAPI document, each named by its operationId. Never a whole generated catalog.
Any HTTP endpointA 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.

A webhook goes the other way: a signed call from a product or an outside service will start a run.

Family products

ProductEndpointState
RepoOpshttps://mcp.repoops.ai/mcpBuilt
PromptComputehttps://mcp.promptcompute.ai/mcpBuilt
ContextFilehttps://mcp.contextfile.ai/mcpBuilt
AI Source of Truthhttps://aisourceoftruth.com/v1/family/factsAPI
Sales as Codenone knownTo confirm
CommitOpshttps://commitops.ai/api/mcpBuilt

Outside products Planned

ProductWayPhase
GitHubRemote MCPFirst
SlackRemote MCP, or the Slack Web APIFirst
LinearRemote MCPFirst
Any webhookA trigger: a signed call from any service starts a runFirst
Any HTTP APIAny HTTP endpointFirst
Jira and ConfluenceRemote MCPSecond
NotionRemote MCPSecond
SentryRemote MCPSecond
HubSpotRemote MCPSecond
StripeRemote MCPSecond
SalesforceAPI actionsSecond
ZendeskAPI actionsSecond
DatadogAPI actionsSecond
Google WorkspaceAPI actionsSecond

Each outside connector reads Planned until it ships. Integrations shows the same list.