pflow mcp command group manages Model Context Protocol (MCP) server connections. MCP servers expose external tools that can be used in pflow workflows.
Setup commands. You run
add, remove, and sync to configure MCP servers. Your agent uses tools and info to discover available tools when building workflows.Commands
pflow mcp add
Add MCP servers from config files or JSON.CONFIG_SOURCE- One or more config file paths or raw JSON strings
Environment variables in
env and headers support ${VAR} and ${VAR:-default} syntax. They expand at runtime.pflow mcp list
List all configured MCP servers.--json- Output as JSON
pflow mcp remove
Remove an MCP server configuration.NAME- Server name to remove
--force, -f- Skip confirmation prompt
Removing a server also removes all its tools from the registry.
pflow mcp sync
Discover and register tools from MCP servers.NAME- Server name to sync (conflicts with--all)
--all, -a- Sync all configured servers
pflow mcp list
List registered MCP tools.SERVER- Filter by server name (optional)
--json- Output as JSON
pflow mcp describe
Show detailed information about an MCP tool.TOOL- Tool name to inspect
pflow mcp serve
Run pflow as an MCP server for AI tools.--debug- Enable debug logging
This is typically invoked by AI tools automatically, not run directly. See the integrations guide for setup instructions.
- Discovering workflows and nodes
- Running workflows
- Validating workflows
- Saving workflows to the library
- Managing settings
Tool naming convention
MCP tools are registered with the patternmcp-{server}-{tool}:
Agents can use the shortest unambiguous name in workflows.
Using MCP tools in workflows
After syncing, MCP tools work like any other node:File locations
Common workflows
Initial setup
Troubleshooting
Related
- Adding MCP servers guide - Detailed setup guide
- CLI overview - Main pflow command
- MCP node reference - Using MCP tools in workflows

