1. Conduid
  2. Agents
  3. ToolFlow
MCP server · Agents

ToolFlow

A runtime-first MCP tool system. No workflow, Python-native tools, dynamic composition, stateless execution with FastMCP.

34Low

Scored 6 months ago · breakdown

About ToolFlow

ToolFlow is an MCP server in the Agents category: a runtime-first MCP tool system. No workflow, Python-native tools, dynamic composition, stateless execution with FastMCP.

Install

From source
git clone https://github.com/whitejoce/ToolFlow

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about ToolFlow

Powered by Claude · Grounded in docs

I know everything about ToolFlow. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README

ToolFlow

中文 | English


Stop building workflows. Write a function, ship a tool.

ToolFlow is a runtime-first MCP tool system for LLM applications. You write plain Python functions — ToolFlow handles versioning, dispatch, isolation, and dynamic composition at runtime.

No DAGs. No pipelines. No restarts. Tools are loaded, executed, and destroyed on demand in isolated sandboxes. Compose them dynamically when called, not when deployed.

Built on Django (control plane) + FastMCP (stateless execution layer).

Key Features

  • 🐍 Python-native tools — write a function, register a tool. No boilerplate.
  • ⚡ Dynamic composition — tools combine at runtime, not at design time.
  • 🔒 Ephemeral sandboxes — every call runs in a fresh in-process sandbox with restricted imports; tool state is not reused across calls, though external side effects (for example, network calls) are still possible.
  • 🧱 Control plane / execution plane separation — Django manages assets; FastMCP executes statelessly.
  • 🔄 Built-in lifecycle management — version, release, and monitor tools independently.

Architecture & Invocation Flow

1. Architecture Flowchart

graph TD
  A[LLM / Client] -->|Tool Call| B[Django Gateway + Control Plane]
  B -->|Fetch Tool Code/Version| C["DB / Storage"]
  B -->|Dispatch Tasks| D{Queue/Dispatcher}
  D --> E[FastMCP Executor 1]
  D --> F[FastMCP Executor N]
  E -->|Ephemeral Load + Execute| G[Ephemeral Tool Runtime Sandbox]
  F -->|Ephemeral Load + Execute| H[Ephemeral Tool Runtime Sandbox]
  E -->|Report Status/Result| B
  F -->|Report Status/Result| B

Project Structure

  • server/: Django gateway and management APIs
  • runtime/: executor, bridge service, and runtime config
  • frontend/: React + Vite frontend
  • start_services.py: one-command local orchestrator

Quick Start

  1. Set up Python environment
python -m venv .venv
.venv\Scripts\activate
pip install -r requirements.txt
  1. Install frontend dependencies
cd frontend
npm install
  1. Initialize database
cd ../server
python manage.py migrate
python preset_tools.py
  1. Return to project root and start all services
cd ..
python start_services.py

Default frontend URL: http://127.0.0.1:5173

Environment Variables

Copy .env.example to .env and configure as needed:

  • DJANGO_SECRET_KEY
  • DJANGO_DEBUG
  • DJANGO_ALLOWED_HOSTS
  • DJANGO_CORS_ALLOWED_ORIGINS

Notes

  • Runtime config file: runtime/config.json
  • MCP Bridge script: runtime/mcp_bridge.py

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About ToolFlow

How do I install ToolFlow?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is ToolFlow safe to use with an AI agent?

Its trust score is 34 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is ToolFlow still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.