We study whether LLMs can produce executable workflow artifacts that remain consistent across graph structure, tool implementation, schema bindings, and runtime wiring. In this setting, correctness depends on cross-layer consistency: a workflow may be structurally plausible, yet still fail because tool implementations, schema bindings, or runtime execution do not align. Existing benchmarks largely evaluate these capabilities in isolation or rely on trajectory-level proxies, leaving open whether generated workflow artifacts execute end-to-end. We introduce MCPGen, an executable benchmark for Model Context Protocol (MCP) workflow development. MCPGen contains 100 self-contained MCP projects across 16 application domains and evaluates three diagnostic tasks: workflow reconstruction, tool creation, and backward-compatible workflow extension. We evaluate 11 representative LLMs in a single-turn foundation-model setting, assessing generated artifacts through static analysis, unit and integration tests, and process-isolated end-to-end execution. Models reach 88.5% on workflow reconstruction, but no model exceeds 57% end-to-end execution success. Per-tool unit-test pass rates reach 63.8%, while project-level integration success does not exceed 45%, suggesting that integration remains a major bottleneck even when isolated tool tests pass.
Figures & tables
Figure 1: Overview of MCPGen tasks. The benchmark evaluates LLMs on reconstructing control flow from shuffled steps, creating executable tools, and extending workflows while preserving backward compatibility.
Benchmark
Workflow & Structure
Evaluation & Data
Code
MCP
Multi-Step
DAG
Conditional
Real-World
Trajectory
Structural
Generation
Native
Tasks
Workflow
Branches
Data Source
Evaluation
Evaluation
Capability
ToolBench Qin et al. (2023)
✗
✓
✗
✗
✓ \
✓ \
✗
✗
API-Bank Li et al. (2023)
✗
✓
✗
✗
✓ \
✓
✗
✗
MCPBench Luo et al. (2025)
✓
✗
✗
✗
✓
✓
✗
✗
LiveMCPBench Mo et al. (2025)
✓
✓
✗
✗
✓
✓
✗
✗
Table 1: Comparison of representative tool-use benchmarks and MCP-focused benchmarks . A check mark indicates that at least one task explicitly evaluates the capability, not exhaustive coverage. Structural Evaluation refers to explicit scoring of workflow graphs, dependencies, or branches; Code Generation Capability refers to executable tool or workflow-artifact generation.
Figure 2: Domain distribution of the 100 MCPGen projects. The outer ring shows 16 application domains; the inner ring groups them by primary data modality.
Category
Metric
Value
Projects & Tools
Projects
100 (16 domains)
Workflow-referenced tools
911 (9.1 / project)
Workflows
Easy (3–5 steps)
17 (17.0%)
Medium (6–10 steps)
50 (50.0%)
Hard (11+ steps)
33 (33.0%)
Task samples
Task 1: Workflow Reconstruction
100 workflows
Table 2: MCPGen dataset statistics.
Figure 3: Per-project MCP tool counts across domains. Each marker is a project and colors indicate difficulty.
Model
Task 1: Workflow Reconstruction
Task 2: Tool Creation
Task 3: Workflow Extension
Order
Depend.
Path Robust.
Overall
Indiv. Pass
Collective Pass
Tool Chain
Data Ref
Edge F1
E2E Success
Gemini-Flash
96.5
88.9
80.2
88.5
41.3
32.0
75.5
41.8
74.3
36
Gemini-Pro
95.6
86.9
77.8
86.7
53.5
34.0
76.3
37.5
73.5
57
Claude-Sonnet
95.5
85.9
76.4
85.9
63.8
41.0
64.9
41.6
71.1
15
Claude-Haiku
93.7
84.0
74.4
84.0
62.3
45.0
56.3
33.3
66.4
10
o3
94.3
84.9
72.4
83.7
56.7
39.0
68.1
38.3
72.9
46
Table 3: Main results on MCPGen across 100 executable MCP projects and 11 LLMs with percentages metrics. Task 2 contains 911 tool-creation targets, one for each distinct tool used by a project workflow; pass rates are computed over targets from projects whose reference workflows execute successfully.
Figure 4: Failure-category distribution over the 743 failed executions with available diagnostic traces.
Weights (Order / Path Robust. / Depend.)
Mean Overall
Spearman ρ
0.40 / 0.40 / 0.20 (default)
86.3
–
0.33 / 0.33 / 0.33
84.4
1.000
0.50 / 0.20 / 0.30
86.1
1.000
0.30 / 0.50 / 0.20
82.4
0.991
0.30 / 0.30 / 0.40
84.4
1.000
Table 4: Sensitivity of Task 1 model rankings to aggregate-metric weights. Rankings remain stable under alternative weightings.
Baseline
Tool Chain
Data Ref
Edge F1
Pre(0.7)
54.0
57.6
54.6
Pre(0.5)
50.0
49.8
56.1
Pre(0.3)
48.2
47.0
59.5
Table 5: Workflow-extension ablation over prefix ratio, evaluated with auxiliary structural metrics.
Figure 5: Case study of a tool-chain integration failure. Two locally valid tools are connected by an invalid workflow edge, causing runtime schema validation.
Figure 6: Error-category distribution by model within the analyzed subset.
Large Language Model (LLM) agents increasingly interact with external systems through tool-calling protocols such as the Model Context Protocol (MCP). In prevailing architectures, the agent must reason about every tool invocation in every session, consuming tokens proportional to the number of actions performed--even when the task has been solved before. We present the MCP Workflow Engine, a novel MCP-native orchestration layer that decouples intelligence (deciding what to do) from execution (carrying it out). An agent reasons once to produce a declarative workflow blueprint--a JSON document specifying a directed sequence of MCP tool calls with parameterized templates, loops, parallel branches, and data piping. Subsequent executions are triggered by a single run_workflow tool call, consuming one invocation's worth of tokens regardless of the blueprint's internal complexity. We formalize the MCP Mediator architectural pattern--an MCP server that simultaneously acts as a client to downstream MCP servers--and implement it in TypeScript against the MCP SDK. We evaluate the engine on a production-scale Kubernetes CMDB synchronization task spanning 67 orchestrated steps across 2 MCP servers, 38 namespaces, 13 worker nodes, and 22 distinct resource types. The engine reduces per-execution token cost by over 99%, completes the full cluster graph--comprising 1,200+ nodes and 2,800+ relationships across 20 relationship types--in under 45 seconds, and achieves deterministic, idempotent execution with zero agent involvement at run time.
Large Language Models (LLMs) are increasingly serving as autonomous agents, and their utilization of external tools via the Model Context Protocol (MCP) is considered a future trend. Current MCP evaluation sets suffer from issues such as reliance on external MCP services and a lack of difficulty awareness. To address these limitations, we propose MCPAgentBench, a benchmark based on real-world MCP definitions designed to evaluate the tool-use capabilities of agents. We construct a dataset containing authentic tasks and simulated MCP tools. The evaluation employs a dynamic sandbox environment that presents agents with candidate tool lists containing distractors, thereby testing their tool selection and discrimination abilities. Furthermore, we introduce comprehensive metrics to measure both task completion rates and execution efficiency. Experiments conducted on state-of-the-art LLMs reveal significant performance differences in handling complex, multi-step tool invocations. All code is open-source at https://github.com/Brunestuder/MCPAgentBench.
Large language model (LLM) agents are increasingly deployed over Model Context Protocol (MCP) servers, yet the benchmarks used to evaluate them score the final answer or a fixed "ground-truth" list of tools, both of which are fragile once the underlying data is live and stateful. We present DynamicMCPBench, a reusable framework rather than a fixed dataset. A practitioner can run it on their own MCP servers to test models on their own tasks, or let it collect servers automatically to measure a model's general ability to solve agentic tasks. Given the servers and any set of models, it generates realistic goals, pursues each one live to record a successful trajectory, distills that trajectory into path-agnostic effect checkpoints, and scores an agent on whether it reproduces those effects, never on the final answer. To show what the framework reveals, we run it at scale: 24 models over 121 servers and 750 tasks spread evenly over 15 task categories (50 each), where each category targets a distinct tool-use challenge of the generated questions. Each task is scored by pass^3: it counts as solved only if all three independent attempts succeed. Even the strongest agents solve only about half of the tasks, 31% of tasks are solved by no model at all, and accuracy collapses as the required tool chain grows longer (from 39% on the shortest chains to 13% on the longest). A human validation study confirms the automatic scoring is reliable (chance-corrected agreement of 0.76). DynamicMCPBench thus turns benchmark construction into something practitioners can rerun on their own servers and models, while exposing a consistent inability of current agents to handle long, multi-step agentic tasks.
Jerzy Kamiński, Ilya Galyukshev, Artem Kuznetsov +4