← Back to directory

Volcano Agent SDK

Community

Build AI agents that combine LLM reasoning with MCP tool calls in a few lines of TypeScript

GitHub source repository ↗

★ 402 Stars Category · Dev Tools Popular Source revision 1d3e13a3aad4

38FMRS · D

Reliability

4/20

Security and permissions

8/20

Maintenance

11/20

Documentation

9/20

Setup experience

6/20

Volcano Agent SDK is a multi-provider AI agent orchestration framework for TypeScript developers that connects to external MCP servers for automatic tool selection and multi-agent coordination, but it is not itself an MCP server exposing tools, and the repository provides no server manifest or fixed tool list.

Read the FMRS scoring method →

Volcano Agent SDK is a TypeScript SDK from Kong for building AI agents that chain LLM reasoning with real-world actions performed through MCP tools. It is important to note this project itself is a client-side orchestration framework, not an MCP server exposing tools — developers connect to external MCP servers via mcp(url) and let the LLM automatically pick which of those servers' tools to call. It supports mixing multiple LLM providers (OpenAI, Anthropic, Mistral, and others), and offers parallel execution, branching, loops, multi-agent coordination (a coordinator agent autonomously delegates tasks to specialized sub-agents), streaming output, OpenTelemetry observability, and built-in retries/timeouts. No server manifest or fixed tool list is provided in the repository, since the available tools depend entirely on whichever external MCP servers a developer connects.

Tools

The tool list has not been reviewed yet.

Setup

Install via npm: npm install @volcano.dev/agent. Then, in TypeScript code, import agent, llmOpenAI (or another provider helper), and mcp; initialize the model with your LLM API key, point mcp("http://host:port/mcp") at an already-running MCP server, chain .then() steps, and call .run(). The SDK does not require or provide a JSON configuration file for clients like Claude Desktop, since it is a library embedded in your own TypeScript application rather than a standalone MCP server process.

Fit and risk

Best for

Backend/platform engineers already using TypeScript who need to orchestrate LLM calls and multiple MCP servers within their own application
Teams building multi-agent delegation workflows (research, writing, task handling, etc.) with autonomous coordination
Teams that need to mix several LLM providers in one workflow with built-in retries, streaming, and tracing

Not for

Users who want an out-of-the-box MCP server that exposes specific business tools (this project provides no tools itself — it requires connecting to external MCP servers)
Developers working in Python or other non-JavaScript/TypeScript stacks
Non-technical users hoping to add it via a Claude Desktop-style configuration file

Required permissions

Requires developer-supplied API keys for the LLM provider(s) in use (e.g., OPENAI_API_KEY)
Requires network access to connect to whatever MCP server endpoints the developer deploys (e.g., http://localhost:8001/mcp)
Because it supports automatic tool selection, it implicitly gains whatever permissions the connected MCP servers grant to their tools

Risks and side effects

Automatic tool selection means the LLM decides which tools to invoke based on the prompt; if connected to MCP servers with real side effects (creating tasks, sending requests), there is a risk of unintended actions from prompt injection or model misjudgment
In multi-agent delegation mode, the coordinator autonomously decides when the workflow is done, which could lead to unexpected repeated calls or resource use if not designed carefully
The README does not describe specific authentication, sandboxing, or permission-isolation mechanisms — the security boundary of connected MCP servers is the developer's responsibility

Troubleshooting

Verify the LLM provider API key environment variables are set correctly
Confirm the server URL passed to mcp() is reachable and the target MCP server is running and listening on the expected port
Consult the official docs at volcano.dev/docs for MCP tool connection pooling and OAuth authentication sections when tools aren't being selected or invoked as expected
Check that the @volcano.dev/agent npm package is up to date, or review the repository's CI status for known build issues

Use cases

Orchestrating an LLM agent that automatically selects and calls tools across multiple deployed MCP servers based on a natural-language prompt

Building multi-agent pipelines where a coordinator agent autonomously delegates work to specialized sub-agents (e.g., a researcher and a writer)

Running production workflows that mix or switch between multiple LLM providers (OpenAI, Anthropic, Mistral, etc.) with built-in OpenTelemetry tracing

Supported clients

Supported clients have not been confirmed yet.

Related MCP servers

Compare with other MCP servers