Developers
Connect your agent
Agents such as Claude Code and Codex use Leaflow through MCP, the CLI or the SDKs. They work in the same project, with the permissions of the account you signed in with, calling the same operations as the Console.
These clients connect today. Any other client that speaks MCP or runs a command works too.
ChatGPT / Codex
Claude CodeCursor
OpenCode
Hermes Agent
OpenClaw
WorkBuddy
- Other clients
Three ways in
Pick one, or use them all. All three call the same operations.
{
"mcpServers": {
"leaflow": {
"command": "leaflow",
"args": ["mcp", "serve"]
}
}
}The MCP server offers four tools: list services, list operations, read an operation definition, and call an operation. The agent reads the constraints in the definition and passes arguments that fit them. It runs over standard input and output by default, or over a network port.
leaflow login
leaflow project use website
leaflow compute list-instances -o json
leaflow compute get-instance web-01leaflow, then the service and the operation name, calls an operation and prints JSON or columns you choose, for scripts. Install with the script, or with go install.
npm i @leaflow/sdk openapi-fetch
go get github.com/leaflowapis/leaflow-go/computeTypeScript uses @leaflow/sdk with openapi-fetch; Go imports the package for each service under github.com/leaflowapis/leaflow-go.
Look up the operation, then call it.
Who confirms a change?
Shipping's changes can wait for your approval. Your own agent uses your account's permissions.
Shipping works from the Console or a chat app and follows the approval setting you chose before changes. Your own agent has no separate approval step: it acts as the account that ran leaflow login, within the selected project. When you only need to look, add --read-only to the command that starts the MCP server, and it stops offering operations that change resources.
Shipping
- Talk to it in the Console or a chat app
- Each change can wait for your approval
- A visible cursor when it operates a page
- Every step listed in the chat
Your own agent
- Calls through MCP, the CLI or an SDK
- Uses the signed-in account and its permissions
- Limited to the selected project
- No credentials of its own, and no access to another account
From install to the first question
- 01
Install the CLI
macOS and Linux.
curl -fsSL https://raw.githubusercontent.com/LeaflowNET/leaflow/main/install.sh | sh - 02
Sign in and choose a project
Signing in happens in the browser. Choose a project after that, and every call stays in it.
leaflow login - 03
Give the agent the MCP server
Add this to the MCP configuration of Claude Code or another agent.
leaflow mcp serve - 04
Ask it something
It reads the operation definition first, then calls it.
leaflow compute list-instances -o json
Arguments and responses are in the reference
Each operation’s arguments, responses and error codes are in the API reference, along with the CLI, MCP and SDK guides.
Start with this sentence.
Copy the prompt below, paste it to your agent, and it will read the install notes and sign in on its own.