Store, query, and create YAML workflow playbooks for LLM agents via MCP. STDIO or Streamable HTTP.
Store, query, and create YAML workflow playbooks for LLM agents via MCP. STDIO or Streamable HTTP. That is what the workflows mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The server publishes 7 tools. What each one is for:
workflow_list — List all permanent workflows in the index, with optional keyword, category, and tag filtersworkflow_get — Retrieve a complete workflow definition by name, with global instructions prependedworkflow_create — Write a new permanent workflow YAML to the libraryworkflow_create_temp — Write a temporary one-shot workflow, indexed but excluded from list resultsworkflow_delete — Permanently remove a permanent workflow by name and optional versionPrerequisites — The Prerequisites tool exposed by this serverInstallation — The Installation tool exposed by this serverConfiguration is passed through the environment: MCP_TRANSPORT_TYPE, WORKFLOWS_DIR, GLOBAL_INSTRUCTIONS_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
workflows-yaml/ seed).Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Among the file and storage access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Workflows's toolset — workflow_list, workflow_get, workflow_create and 4 more — is a fair guide to whether it matches your workflow. It is maintained by cyanheads; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Workflows's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| workflow_list | List all permanent workflows in the index, with optional keyword, category, and tag filters. |
| workflow_get | Retrieve a complete workflow definition by name, with global instructions prepended. |
| workflow_create | Write a new permanent workflow YAML to the library. |
| workflow_create_temp | Write a temporary one-shot workflow, indexed but excluded from list results. |
| workflow_delete | Permanently remove a permanent workflow by name and optional version. |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | The Installation tool exposed by this server. |
{
"mcpServers": {
"workflows-mcp-server": {
"type": "stdio",
"command": "bunx",
"args": ["@cyanheads/workflows-mcp-server@latest"],
"env": {
"MCP_TRANSPORT_TYPE": "stdio",
"WORKFLOWS_DIR": "/absolute/path/to/your/workflows-yaml"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
workflows-yaml/ seed).| Variable | Description | Required |
|---|---|---|
| MCP_TRANSPORT_TYPE | Configuration value read at startup. | Optional |
| WORKFLOWS_DIR | Filesystem location the server is allowed to use. | Optional |
| GLOBAL_INSTRUCTIONS_PATH | Filesystem location the server is allowed to use. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.