Download the PHP package particle-academy/fancy-flow-mcp without Composer
On this page you can find all versions of the php package particle-academy/fancy-flow-mcp. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download particle-academy/fancy-flow-mcp
More information about particle-academy/fancy-flow-mcp
Files in particle-academy/fancy-flow-mcp
Package fancy-flow-mcp
Short Description A Laravel MCP server that lets an AI agent build fancy-flow workflows headlessly — list node kinds, add/connect/configure nodes, validate, export the WorkflowSchema, and run — as a thin, deterministic wrapper over particle-academy/fancy-flow-php.
License MIT
Homepage https://github.com/Particle-Academy/fancy-flow-mcp
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package fancy-flow-mcp
fancy-flow-mcp
A Laravel MCP server that lets an AI agent build fancy-flow workflows headlessly.
Built on laravel/mcp (Laravel's official MCP
package) and powered by
particle-academy/fancy-flow-php
(the PHP runtime twin of fancy-flow). The connecting model is the only
intelligence involved — every tool here is a thin, deterministic wrapper over
fancy-flow-php's schema, registries, validation, and engine. No LLM calls, no
network, no guessing.
An agent discovers the node kinds, creates a workflow, adds and wires nodes (connections are port-validated), fills in each node's config (schema-checked), validates the whole graph, and exports a portable WorkflowSchema v1 JSON — the same document
<FlowEditor>imports and both the Node and PHP engines run unchanged.
Requires PHP 8.3+ (fancy-flow-php's floor) and Laravel 12 or 13
(laravel/mcp needs illuminate/json-schema, which ships in framework 12+).
The tools
| Tool | What it does |
|---|---|
list_node_kinds |
Every authorable kind — id, category, label, ports, aliases. Optional category filter. |
describe_node_kind |
One kind's full config schema, ports, defaults, and aliases. |
create_workflow |
Start an empty draft; returns a workflow_id used by every later call. |
import_workflow |
Load an existing WorkflowSchema document into an editable draft (lenient — reports issues, doesn't reject). |
get_workflow |
Inspect the current draft — metadata, nodes, edges. |
list_workflows |
Every draft the server holds. |
delete_workflow |
Discard a draft. |
add_node |
Add a node of a kind; config defaults applied, config schema-checked. |
configure_node |
Set/merge a node's config, re-validated against its kind. |
connect_nodes |
Draw a port-validated edge (handles default out → in). |
remove_node |
Delete a node and cascade its edges. |
remove_edge |
Delete a single edge. |
validate_workflow |
Authoritative Workflow::import check (unknown kinds, missing config, dangling edges) + host capability status. |
export_workflow |
The deliverable: canonical WorkflowSchema v1 JSON. |
run_workflow |
Smoke-test the graph with fancy-flow-php's deterministic fake executors. |
Plus a resource — flow://node-kinds — carrying the entire kind catalogue as
one JSON document, so an agent can pull it once as context.
Why "port-validated" connections matter
Workflow::import() validates that an edge's endpoints exist; it does not
check that a handle is a real port. connect_nodes adds that: a branch needs
source_handle "true" or "false", a merge needs target_handle "a" or
"b", a terminal output can't be a source, a trigger can't be a target — and
when you get it wrong, the error names the valid ports. Dynamic-port kinds are
resolved from config the way the engine documents them (llm_router routes,
switch_case cases, subflow stream mode).
Registering the server
The service provider registers a local (stdio) server named fancy-flow out
of the box, so it works with a desktop AI client immediately:
Publish the config to customize:
To expose it over HTTP instead (protect it — an MCP endpoint runs tools on your
app), set web.path (e.g. /mcp/fancy-flow) and appropriate middleware, or
register it yourself in routes/ai.php:
The draft store
An agent authors a workflow across many tool calls, so drafts persist between
them via a DraftStore. cache (default) survives the request-per-call
lifecycle of a web server; array keeps drafts in-process, which is fine for
a long-lived local/stdio server. Rebind FancyFlow\Mcp\Store\DraftStore in
your app to persist to a database instead.
A typical build
Testing
The suite has framework-free unit tests (the authoring core + port resolver) and
feature tests that drive the real MCP tools through FlowBuilderServer.
Local development note
particle-academy/fancy-flow-php is not yet published to Packagist. Until it is,
composer.json carries a local path repository pointing at ../fancy-flow-php
(its sibling in the Fancy suite envelope). When fancy-flow-php ships, drop that
repositories block and the dependency resolves from Packagist as ^0.x.
License
MIT © Particle Academy
All versions of fancy-flow-mcp with dependencies
ext-json Version *
laravel/mcp Version ^0.9
particle-academy/fancy-flow-php Version >=0.48 <2.0