MCP and Developers

    One MCP server for all your flows.

    Point Claude, Cursor or any MCP client at one address. Your AI assistant can run your active flows, check how a run went, and draft new flows for you to review.

    Exomations MCP ServerExample
    https://exomations.com/api/mcp
    exo_list_flows
    exo_get_execution
    exo_create_flowsaved as draft
    exo_overdue_reminders_7a17617d

    Every active flow is a tool

    The assistant sees your flows by name and calls them with the inputs they expect, except flows with government identity or write steps, until you allow them.

    Drafts first, production by a person

    Flows the assistant creates or edits are saved as drafts for a person to review. A person moves a flow to staging and activates it; with the build permission the assistant can activate a flow that is already in staging. Production always takes a person.

    Keys with permissions

    An API key needs execute to run flows and build to draft them. OAuth works too.

    Built for developers and AI tools.

    API keys with permissions

    Create a key for each use and give it only what it needs.

    API KeysExample
    Claude Desktopexo_4f2a...executeActive
    Cursorexo_91be...execute buildActive
    Reportingexo_c07d...readActive
    Permissions: Execute Flows · Read Data · Build (MCP authoring)

    Webhooks in

    Start a flow from your own system and verify the signature.

    Webhook triggerExample
    POST /api/trigger/7a17617d… X-Api-Key: exo_4f2a... X-Webhook-Signature: 9f2c…
    ***

    Code step

    JavaScript in a locked-down sandbox, for the step no block covers.

    CodeExample
    const overdue = input.invoices.filter(i => (Date.now() - new Date(i.DocDueDate)) / 864e5 > 30); return { count: overdue.length, total: overdue.reduce((s, i) => s + i.DocTotal, 0) };

    Git sync

    Keep flow definitions in your own repository.

    Git SyncExample
    GitHub
    main
    github.com/acme/flows
    flows/overdue-reminders-7a17617d.json
    Test ConnectionSync All Flows Now

    Environments

    Keep development, staging and production apart, and promote when ready.

    ConnectionsExample
    Current Environment
    AllDevelopmentStagingProduction
    SASAP Business OneCredentials: ***Staging
    → Production

    Connect any MCP server. Call any AI tool.

    Exomations now speaks MCP — the open standard for AI tool servers. Plug in a server URL, pick a tool, and use it in any flow alongside your other nodes.

    One-click MCP connection

    Add an MCP server like any other connection — pick the transport (HTTP or SSE), paste an optional token, and you're live.

    Any tool, any flow

    The new MCP Tool Call node lists the tools your server exposes and lets you call them with variables from earlier steps.

    Safe by default

    Tenant-scoped credentials, encrypted at rest, with built-in protection against private-network calls (SSRF).

    Available on every plan. Works with the Anthropic, OpenAI, and any open-source MCP server.

    Common questions

    What is MCP?

    The Model Context Protocol is an open standard that lets AI assistants such as Claude or Cursor use outside tools. Exomations exposes your flows as those tools.

    How do we connect a client?

    Add the address https://exomations.com/api/mcp to your client with an API key in the X-Api-Key header, or sign in with OAuth.

    Can the assistant change a live flow?

    No. What it creates or edits is saved as a draft. A flow that is live keeps running on its published version until a person publishes the change.

    Connect your AI assistant to your flows.

    7-day trial1 SAR card checkHosted in Riyadh