Flowdesk MCP
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Flowdesk MCP
A free, local-first alternative for Pabbly Connect-style workflows. Receive a JSON event, filter it, transform fields, save a record and forward the result to an HTTPS receiver. Build the same workflow in a browser or through an MCP client. The editor, webhook handler and MCP server share a SQLite database.
Run the editor
Use Python 3.11 or newer. From a terminal:
git clone https://github.com/akash-decoder/flowdesk-mcp.git
cd flowdesk-mcp
python -m venv .venvActivate the environment with source .venv/bin/activate on macOS/Linux or .venv\Scripts\activate.bat in Windows Command Prompt. Then run:
python -m pip install .
flowdesk webOpen http://127.0.0.1:8765. The initial Lead intake draft accepts website inquiries, builds a subject line and stores the transformed record. Choose Save workflow, then Preview. The sample produces Quote request from Alex. Choose Run now and open Records to see the saved result. Change service to print and run again to see a filtered event in Run history.
Related MCP server: Procesio MCP Server
Connect an MCP client
For a desktop client that supports stdio, add this entry to its MCP server configuration. Replace the command with the absolute path to the installed Python interpreter. On Windows use a path such as C:/projects/flowdesk-mcp/.venv/Scripts/python.exe. Restart the client after saving.
{
"mcpServers": {
"flowdesk": {
"command": "/absolute/path/to/flowdesk-mcp/.venv/bin/python",
"args": ["-m", "flowdesk", "mcp"]
}
}
}Try asking your client:
Find my Lead intake workflow. Preview it with name Alex and service website. Show me the transformed record.
Tool | Operation |
| Read definitions, IDs and revisions |
| Create a named workflow with ordered steps |
| Save edits against an expected revision |
| Evaluate an input without writing history or triggering actions |
| Execute a workflow with an optional idempotent event ID |
| Read the latest 50 run outputs and step traces |
| Read the latest 100 saved records |
| Read the latest 100 outbound delivery states |
Receive an event
Save a workflow and open Inbound webhook → Show connection details in the editor. Supply the displayed workflow ID and key in your sender. For example, in a POSIX shell:
curl -X POST "http://127.0.0.1:8765/hooks/$WORKFLOW_ID" \
-H "Content-Type: application/json" \
-H "X-Flowdesk-Key: $WORKFLOW_KEY" \
-H "Idempotency-Key: inquiry-001" \
-d '{"name":"Alex","service":"website"}'Retries with the same event ID and payload return the original run. Reusing the ID with different input returns HTTP 409. A processed event returns the run ID and workflow status. A filtered or failed workflow commits its run trace and creates zero records or deliveries.
Send to another app
Add a Send webhook step and give it a destination alias, for example crm. Its body is the current JSON object. Start a worker from the same environment and OS user. Replace the example URL with the HTTPS webhook URL of your receiver.
export FLOWDESK_TARGETS='{"crm":"https://receiver.example/webhooks/intake"}'
flowdesk workerOn PowerShell, set $env:FLOWDESK_TARGETS = '{"crm":"https://receiver.example/webhooks/intake"}' and run flowdesk worker. Keep destination URLs with embedded credentials private. The worker sends each delivery with an Idempotency-Key header. Workflow completion queues the delivery. Its eventual HTTP outcome appears under Deliveries. A transport failure or an interrupted send is marked unknown after reconciliation. Check the receiver before manually resubmitting an event with a new ID.
Operating scope
MIT-licensed software with no subscription or per-run billing. Hosting and external services have their own terms and costs.
Designed for one trusted local user. The editor listens on loopback. Local processes can read workflow data and webhook keys. For an external sender, forward only the specific
POST /hooks/<id>endpoint through an HTTPS reverse proxy, forwarding the internal Host as127.0.0.1. Keep the editor and/apilocal.All three processes use
~/.flowdesk/workspace.sqlite3by default. To share another location, give each process the same absoluteFLOWDESK_DBpath. Keep the database private and stop all three processes before copying its directory for a backup.Templates reference top-level JSON fields with
{{field}}. Filters compare a field with a string using exact equality. A saved record captures the payload at that step. A workflow supports 24 ordered steps and 64 KiB input/output objects.This release focuses on workflow automation. The wider Pabbly suite, its native integration catalog, scheduling and OAuth account management are outside the implementation. Public product review
Tests
python -m unittest discover -s tests -vThe tests exercise the editor API, concurrent webhook retries, filter and failure behavior, outbound delivery with a mock HTTPS receiver, and a real MCP client/server exchange over stdio. For the desktop/mobile browser smoke test, install Playwright, run python -m playwright install chromium, then python tests/browser_smoke.py.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Build and run AI workflows, agents, data tables and 1000+ API integrations from any MCP client.
Inspect and edit media canvases, run existing Flows, and retrieve results. Vyrl MCP token required.
A managed runtime for custom API integrations. Manage lines, endpoints, keys, logs and DLQ via MCP.
Governed data discovery, exact queries, decisions, simulations, and runtime utilities over MCP.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables management of multiple N8N workflow automation instances through MCP. Supports listing, creating, updating, deleting, executing workflows and monitoring their executions across different N8N environments.128 npmMIT
- AlicenseBqualityDmaintenanceEnables interaction with the Procesio automation platform to list, view, and manage workflows. It allows users to launch process instances and monitor their status through MCP-compatible clients.12Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables interaction with the hosted PacedLoop API to manage workflows and monitor process runs. It provides tools for workflow CRUD operations, run execution management, and access to detailed performance analytics within MCP-capable clients.-
- AlicenseNot gradedqualityCmaintenanceMCP server for authoring, validating, simulating, and publishing workflows for the Runbook workflow engine, including branch and run management.MIT