servflowai command, what each one is for, and what shape of data it reads or prints. Use it with Configuration, Available entry handlers, Available actions, Available integrations, and Available providers.
The settings of one entry handler, action, integration, or provider are not on this page. Each has its own section on its catalog page: Available entry handlers, Available actions, Available integrations, and Available providers.
Commands
server
Runs the HTTP server and dashboard.resource
Reads and writes saved resources and prints the catalogs the server uses.Nouns and verbs
Common flags
The body for create and update
Agent
Integration
Each field ofconfig is an object holding a literal, as value, or the name of a stored secret, as secret. The fields of each type are on Available integrations.
Each integration body takes a user-facing name. ServFlow generates the integration’s internal integrationId from that name when it is created and returns it in the result. Updates keep the same integrationId even if you rename the integration later.
OAuth-guided integrations, such as notion_mcp, have no config fields in the body. Creating one this way leaves it unusable until you complete its sign-in in the dashboard. A created integration is stored disabled; servflowai resource integration enable <integrationId> is what serves it.
Provider
config holds the type’s fields as plain values. api_key is the key itself, not the name of a secret. The fields of each type are on Available providers.
Workspace
Secret
A secret takes flags, not a body.The shape of an agent
The document underconfig. servflowai resource agent schema prints the same shape as JSON Schema, and is the authority when this page and the binary differ.
install
Installs a template into the running server.MCP server tools
ServFlow serves the management MCP server at/api/mcp. Send your auth token in the Authorization header, as Bearer <token>.
The management MCP server exposes these tools:
list_actions lists every built-in action type. describe_action describes one or more action types and returns their schema and field metadata. config_schema returns the stored config shape as JSON Schema, and config_example returns a complete example config you can adapt. list_entry_handlers lists every built-in entry type. describe_entry_handler describes one or more handler types and returns their fields, injected variables, and whether each is a listener. list_template_functions lists the template functions available in dynamic content and tool guards, optionally filtered by category.