AI agents

Give an agent the LatidoFlow operating model and a safe management connection.

Use the LatidoFlow plugin when your agent supports it, connect the hosted MCP server directly from any compatible client, or let a code agent integrate the language-neutral REST contract.

Choose an agent setup path

Plugin-capable agent

Search the agent's plugin catalog for LatidoFlow. Installing it supplies the LatidoFlow skill and hosted MCP mapping together. If it is not listed, use direct MCP setup.

MCP client

Add the hosted Streamable HTTP endpoint, complete browser OAuth, then discover tools and the capability resource at the start of each session.

Code agent

Give the agent the OpenAPI contract and the target codebase. Use REST ingestion for runtime evidence and OAuth only for supported management calls.

Connect the hosted MCP server

1. Add the server. Use your client's native remote-MCP configuration and the exact endpoint below.
2. Authorize in the browser. Sign in to the intended LatidoFlow account and confirm the email shown on the consent screen. Approving the mcp:use scope gives the client delegated management access to every LatidoFlow workspace the signed-in account can access, subject to existing workspace roles and policies.
3. Discover before acting. List tools and resources, read latidoflow://capabilities, and inspect the selected tool's live schema and annotations.
4. Resolve the workspace. List accessible workspaces and use the exact workspace UUID for every scoped call. Never infer a workspace from a display name alone.

{
  "mcpServers": {
    "latidoflow": {
      "url": "https://www.latidoflow.com/mcp/latidoflow"
    }
  }
}

Do not paste an ingestion credential into an MCP client. The MCP connection uses customer OAuth. Ingestion credentials belong only in the monitored runtime.

Supported agent actions

Access Available actions

Read

List workspaces; read a workspace overview; list monitors, runs, incidents, status pages, and notification channels. Responses are allowlisted and omit secrets, raw telemetry, endpoint URLs, logs, and customer payloads.

Manage monitors

Synchronize heartbeat or uptime definitions and pause or resume a monitor. Definition sync changes configuration; it does not create runtime proof.

Respond

Acknowledge, silence, unsilence, or close an incident by operator override with a reason; publish a status update; schedule or cancel maintenance.

Configure routing

List or create notification channels and change enabled or scheduled-canary state. Provider contact may be asynchronous, so verify delivery evidence separately.

Credentials

List redacted workspace credentials; issue, begin rotation, complete cutover, or revoke. Issue and rotation-start reveal one plaintext secret once.

The MCP server does not create queued, started, heartbeat, success, failure, skipped, or log evidence. Those facts can arrive only through separately authenticated runtime ingestion.

Confirm writes and read them back

Inspect first. Resolve the workspace and existing resource UUID, then show the intended change and expected effect.
Confirm the exact action. Every mutation requires literal confirmed: true. Pausing, publishing, maintenance, credential changes, and provider-contacting actions deserve immediate explicit confirmation.
Execute once. Do not automatically retry a write unless its live annotations and schema establish idempotency.
Read back. Compare workspace UUID, resource UUID, stable identity, state, and timestamps with the requested target. Treat acceptance of asynchronous work as scheduling, not completion.

Useful agent prompts

Use LatidoFlow to inspect this codebase, propose one heartbeat monitor for the nightly invoice sync, and show me the exact files and REST calls before editing.

List the LatidoFlow workspaces I can access, read the capability resource, and summarize open incidents in the workspace I select. Make no changes.

Prepare an acknowledgement for incident UUID … with reason …, show the target and effect, and wait for my confirmation before executing it.

Verify whether the invoice-sync integration is configured, instrumented, active, or operational. Do not treat definition sync or a simulation as runtime proof.

Troubleshoot or disconnect

If authorization fails, confirm the customer is signed in with a verified email and the client is requesting the hosted endpoint, not an ingestion route.
If a tool is absent, refresh the server's tool list and capability resource. Do not substitute an unrelated action.
If a resource is not found, list accessible workspaces again and verify the explicit workspace and resource UUIDs.
To disconnect, remove or disable the MCP server in the client and revoke the client's OAuth access according to the client's account controls. Rotate an ingestion credential separately if it was ever exposed outside its intended runtime.

OpenAPI contract Runtime integration