Overview
Felix exposes an MCP (Model Context Protocol) server that lets AI assistants create, manage, and run workflows on your behalf. Any MCP-compatible client — Claude Code, Claude Desktop, Cursor, or custom agents — can connect to it. The MCP server provides the same capabilities as the REST API, packaged as tool calls that AI models can invoke directly.Endpoint
x-api-key header as the REST API.
Connecting from Claude Code
Connecting from Claude Desktop
Add to your Claude Desktop config file (~/Library/Application Support/Claude/claude_desktop_config.json on Mac):
Available Tools
| Tool | Description |
|---|---|
list_workflows | List or search workflows in your organization (paginated) |
get_workflow | Get workflow details including input schema and required integrations |
create_workflow | Create a workflow from a prompt and start the planning agent |
run_workflow | Execute a workflow and wait for results (metadata by default, optionally inline content) |
get_execution | Get execution status and results (includes inline content by default) |
list_executions | List executions for a workflow (paginated) |
create_workflow
Creates a new workflow and starts the planning agent to design it based on your prompt. Parameters:| Parameter | Type | Required | Description |
|---|---|---|---|
prompt | string | Yes | What should this workflow do? |
name | string | No | Workflow name (defaults to auto-generated) |
description | string | No | Workflow description |
"planning".
run_workflow
Executes a workflow and waits for it to complete (up to 10 minutes). Returns execution metadata (status, IDs, output filenames, and presigned URLs). Useget_execution to fetch inline file content when needed, or pass include_outputs: true to get it in the same call.
If the workflow has an input schema (human checkpoint on step 1), you must provide matching input data.
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
workflow_id | string (uuid) | Yes | The workflow to execute |
input | object | No | Input data matching the workflow’s input_schema |
wait | boolean | No | Wait for completion (default: true). Set false for fire-and-forget. |
include_outputs | boolean | No | Include inline file content in results (default: false). |
include_outputs is true, text-based files also include inline content.
get_execution
Retrieves the current status of an execution. When status isfinished, includes result files with inline text content and presigned download URLs (valid for 1 hour) by default.
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
workflow_id | string (uuid) | Yes | The workflow ID |
execution_id | string (uuid) | Yes | The execution ID |
include_outputs | boolean | No | Include inline file content in results (default: true). Set false to get metadata only. |
list_workflows / list_executions
Both support pagination vialimit (1-100) and cursor parameters.
get_workflow
Returns workflow details includinginput_schema (JSON Schema) if the workflow’s first step is a human checkpoint, and required_integrations listing any external services the workflow needs.
Example: End-to-End with Claude Code
run_workflow waits for completion by default, the AI assistant gets the results in a single step — no polling loop needed.
