Falcon Builder

dev.falconbuilderv0.1.0Updated Oct 2, 2026

Build, debug, and publish production AI agent workflows in Falcon Builder from any MCP client.

VerifiedStreamable HTTPWeb executableAI & MLDeveloper Tools

Overview

AI-generated overview

Lets an assistant inspect, edit, run, and publish AI agent workflows in a Falcon Builder workspace.

What it does
A hosted MCP server for the Falcon Builder agent platform. Read tools list and inspect agents, workflows, definitions, nodes, executions, logs, version history, and interfaces. Edit tools create, edit, duplicate, and delete workflows and interfaces; run tools execute workflows and rerun executions; publish tools deploy drafts and roll back to earlier versions. Permissions are chosen when connecting, and run and rollback require an explicit confirm flag.
When to use it
Useful when you build or operate Falcon Builder agents and want an assistant to debug failed runs, adjust drafts, validate and publish workflows, or roll back a production version without leaving the chat client.
Requirements
A remote Streamable HTTP endpoint; nothing to install locally. OAuth clients such as claude.ai, Claude Desktop, and ChatGPT register automatically with no token. Other clients need a Falcon Builder API token sent in the Authorization header, created under Settings, Developer; each workspace allows up to 10 active tokens. Network access to the Falcon Builder service is required.
Before you install
The Authorization token is a secret shown only once and grants the permissions chosen at creation, so store it securely. Edit, publish, rollback, and delete tools change workspace state, and publishing or rolling back affects production. Running workflows consumes plan limits. Prefer read-only or draft permissions unless production changes are intended.

Installation

In SourceWeft

  1. Open Falcon Builder in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "falcon-builder": {
      "type": "http",
      "url": "https://www.falconbuilder.dev/api/mcp"
    }
  }
}

README

Falcon Builder MCP Server

Build, edit, and publish production AI agents from Claude, Cursor, ChatGPT, VS Code, or any MCP client. The Falcon Builder MCP server lets your assistant inspect executions, edit and duplicate workflows, run them, and publish them in your Falcon Builder workspace.

Available on every plan, including Free.

This is a hosted server. Nothing to install or run locally.

[smithery badge]

Connect

OAuth clients: claude.ai, Claude Desktop, ChatGPT

No token needed. The client registers itself automatically.

claude.ai / Claude Desktop

  1. Settings → Connectors → Add custom connector
  2. Server URL: https://www.falconbuilder.dev/api/mcp
  3. Leave OAuth Client ID and Client Secret empty
  4. Pick a workspace and the permissions to grant, then approve

ChatGPT Settings → Connectors → Create (turn on Developer Mode if prompted). Same URL, OAuth fields left empty.

Token clients: Claude Code, Cursor, VS Code, Gemini CLI

Create a token first: Falcon Builder → Settings → Developer, name it, choose permissions, and copy it. Tokens are shown once. Each workspace can have up to 10 active tokens.

Claude Code

bash
claude mcp add --transport http falcon-builder \  https://www.falconbuilder.dev/api/mcp \  --header "Authorization: Bearer YOUR_TOKEN"

Cursor (.cursor/mcp.json)

json
{  "mcpServers": {    "falcon-builder": {      "url": "https://www.falconbuilder.dev/api/mcp",      "headers": { "Authorization": "Bearer YOUR_TOKEN" }    }  }}

VS Code (.vscode/mcp.json). VS Code prompts for the token and stores it securely.

json
{  "inputs": [    {      "type": "promptString",      "id": "falcon-token",      "description": "Falcon Builder API token (Settings > Developer)",      "password": true    }  ],  "servers": {    "falcon-builder": {      "type": "http",      "url": "https://www.falconbuilder.dev/api/mcp",      "headers": { "Authorization": "Bearer ${input:falcon-token}" }    }  }}

Gemini CLI (~/.gemini/settings.json). Use httpUrl; in Gemini CLI, url means SSE.

json
{  "mcpServers": {    "falcon-builder": {      "httpUrl": "https://www.falconbuilder.dev/api/mcp",      "headers": { "Authorization": "Bearer YOUR_TOKEN" }    }  }}

Permissions

You choose these when you connect over OAuth or create a token. Read is always included.

PermissionWhat it allows
ReadInspect workflows, executions, logs, version history, and interfaces
Edit draftsChange workflow drafts and configure interfaces without touching production
Run workflowsExecute workflows with test input. Runs count against your plan limits
Publish & rollbackDeploy drafts to production and restore earlier versions

Tools

Read whoami, switch_workspace, list_agents, list_workflows, get_workflow, get_workflow_definition, get_workflow_node, validate_workflow, list_executions, get_execution, get_execution_logs, list_workflow_versions, list_interfaces, get_interface

Edit drafts create_workflow, edit_workflow, duplicate_workflow, duplicate_agent, create_interface, update_interface, add_interface_access_rule, remove_interface_access_rule, delete_interface

Run workflows run_workflow, rerun_executions

Publish & rollback publish_workflow, rollback_workflow, publish_interface

Every tool declares MCP annotations (read-only, destructive, idempotent, open-world), so clients that honor them can ask before anything changes. run_workflow and rollback_workflow also require an explicit confirm: true.

Things to ask your assistant

  • "Why did the last run of my intake workflow fail? Show me the node that errored."
  • "Duplicate my support agent and change its escalation step to email the on-call address."
  • "Validate the draft of my lead-routing workflow, then publish it."
  • "Roll my onboarding workflow back to the previous version."

About

Falcon Builder is built by NeoSky AI.

Source: README.md at commit ea1bd01

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.0LatestOct 2, 2026