# FlowForge

> FlowForge is self-hosted workflow automation (like n8n or Zapier) that runs on ordinary PHP shared hosting with one cron job. It connects 1,190 apps (5,783 actions, 615 triggers) on a visual canvas, has an AI workflow builder, and an MCP server so AI agents can build and run workflows.

This is the FlowForge instance at https://flowforge.sarimtools.com. Its workflows, credentials and runs are private to its team; the endpoints below are for people and agents with an account.

## For AI agents

- [MCP server](https://flowforge.sarimtools.com/api/mcp): Streamable HTTP, JSON-RPC 2.0 over POST. Send `Authorization: Bearer <token>`; a signed-in user creates the token under Settings → API & MCP, and the agent gets that user's permissions.
- [Full reference](https://flowforge.sarimtools.com/llms-full.txt): how workflows are built (triggers, steps, `{{ steps.<id>.<field> }}` data mapping, config formats), every MCP tool with its parameters, and the complete app catalog.

## MCP tools

- `search_apps`: Find integrations by name, purpose or action (e.g. "send sms", "google sheets"). Returns app keys with their action and trigger keys.
- `get_app`: Input definitions of an app's actions/triggers. Format "key*:type=default" (* = required, select options in []). Ask only for the ops you need.
- `list_workflows`: All workflows: id, name, active, trigger type, step count.
- `get_workflow`: Full definition of one workflow (nodes with config, edges).
- `save_workflow`: Create (omit id) or replace (give id) a workflow. Send the complete node and edge list; positions are computed. Returns warnings to relay or fix.
- `set_workflow_active`: Turn a workflow on (its trigger runs it in the background) or off.
- `delete_workflow`: Ask to delete a workflow. The user must confirm in the UI; nothing is deleted until then.
- `list_templates`: Ready-made workflows (key, name, apps). Prefer use_template when one fits the request — it is cheaper than building from scratch.
- `use_template`: Create a workflow from a template. Returns its id and what the user must fill in; adjust it afterwards with save_workflow if needed.
- `list_credentials`: Saved credentials (id, name, app). Optionally filter by app key.
- `test_workflow`: Run a workflow now with its test data and get a per-step result. This performs real actions (emails, messages, API writes): only use when the user asked, or the steps are read-only.
- `get_execution`: Per-step result of a past run (to explain or fix a failure).

## Connect from Claude Code

```
claude mcp add --transport http flowforge https://flowforge.sarimtools.com/api/mcp --header "Authorization: Bearer <token>"
```

## Optional

- [Sign in](https://flowforge.sarimtools.com/login)
- [Sitemap](https://flowforge.sarimtools.com/sitemap.xml)