Tool Chainer▌

by thirdstrandstudio
Tool Chainer connects multiple MCP tools, streamlining complex workflows efficiently with reduced token usage.
Chains multiple MCP tools together in sequence, passing results between tools without sending large intermediate data back to the LLM, reducing token usage for complex workflows.
best for
- / Complex workflows requiring multiple tool calls
- / Reducing token costs in multi-step processes
- / Automating data processing pipelines
- / Developers building MCP tool orchestration
capabilities
- / Chain multiple MCP tools in sequence
- / Pass results between tools using CHAIN_RESULT placeholder
- / Filter data using JsonPath with inputPath/outputPath
- / Discover available tools from configured MCP servers
- / Execute complex workflows with minimal token usage
what it does
Chains multiple MCP tools together in sequence, passing results between them without sending large intermediate data back to the LLM to reduce token usage.
about
Tool Chainer is a community-built MCP server published by thirdstrandstudio that provides AI assistants with tools and capabilities via the Model Context Protocol. Tool Chainer connects multiple MCP tools, streamlining complex workflows efficiently with reduced token usage. It is categorized under productivity, developer tools.
how to install
You can install Tool Chainer in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Tool Chainer is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
MCP Tool Chainer
An MCP (Model Context Protocol) server that chains calls to other MCP tools, reducing token usage by allowing sequential tool execution with result passing. Designed to solve https://github.com/modelcontextprotocol/specification/issues/215
Step function like JSON paths:
Features
- Chain multiple MCP tools together in sequence
- Pass results from one tool as input to another tool using
CHAIN_RESULTplaceholder - Filter and extract specific data using JsonPath with
inputPathandoutputPathparameters - Automatic tool discovery from configured MCP servers
- Minimal token usage compared to individual tool calls
Tools
This server implements the following MCP tools:
mcp_chain- Chain together multiple MCP serverschainable_tools- Discover tools from all MCP servers so the mcp_chain tool can be useddiscover_tools- Rediscover tools from all MCP servers
Installation
Prerequisites
- Node.js (v16 or later)
- npm
Installing from npm
# Install
npm install @thirdstrandstudio/mcp-tool-chainer
# Or use with npx directly
npx -y @thirdstrandstudio/mcp-tool-chainer
Installing from source
# Clone the repository
git clone https://github.com/thirdstrandstudio/mcp-tool-chainer.git
cd mcp-tool-chainer
# Install dependencies
npm install
# Build the package
npm run build
Usage with Claude Desktop, Cursor etc
ENSURE IT IS THE LAST MCP TO RUN OTHERWISE IT WILL HAVE TO RUN DISCOVERY AGAIN
Add the following to your claude_desktop_config.json or mcp.json:
If installed from npm globally
{
"mcpServers": {
"mcp_tool_chainer": {
"command": "npx",
"args": ["-y", "@thirdstrandstudio/mcp-tool-chainer", "`claude_desktop_config.json` or `mcp.json`"],
"env": {}
}
}
}
If installed from source
{
"mcpServers": {
"mcp_tool_chainer": {
"command": "node",
"args": ["/path/to/mcp-tool-chainer/dist/index.js", "`claude_desktop_config.json` or `mcp.json`"],
"env": {}
}
}
}
Replace /path/to/mcp-tool-chainer with the actual path to your repository.
Examples
Chain Browser and XPath Tools
// Fetch a webpage and then extract specific content with XPath
const result = await callTool("mcp_chain", {
"mcpPath": [
{
"toolName": "mcp_browser_mcp_fetch_url",
"toolArgs": "{"url": "https://example.com"}"
},
{
"toolName": "mcp_xpath_xpath",
"toolArgs": "{"xml": CHAIN_RESULT, "query": "//h1"}"
}
]
});
Using JsonPath with InputPath and OutputPath
// Fetch a webpage, extract specific content with XPath, then extract part of the result
const result = await callTool("mcp_chain", {
"mcpPath": [
{
"toolName": "mcp_fetch_fetch",
"toolArgs": "{"url": "https://api.example.com/data"}"
},
{
"toolName": "web_search",
"toolArgs": "{"search_term": CHAIN_RESULT}",
"inputPath": "$.results[0].title", // Extract only the first result's title from previous output
"outputPath": "$.snippets[*].text" // Extract only the text snippets from the search results
},
{
"toolName": "another_tool",
"toolArgs": "{"content": CHAIN_RESULT}"
}
]
});
JsonPath Support
MCP Tool Chainer now supports AWS Step Functions-style InputPath and OutputPath features:
- inputPath: JsonPath expression to extract specific portions of the input before passing to a tool
- outputPath: JsonPath expression to extract specific portions of the output before passing to the next tool
These features work only when the input/output is valid JSON. If JsonPath extraction fails, the original input/output is used.
For JsonPath syntax reference, see JsonPath Syntax.
Benefits
- Reduced Token Usage: By chaining tools together, you avoid sending large intermediate results back to the LLM
- Simplified Workflows: Create complex data processing pipelines with a single tool call
- Improved Performance: Reduce latency by minimizing round-trips between the LLM and tools
- Precise Data Flow Control: Extract only the data you need with JsonPath expressions
Development
# Install dependencies
npm install
# Start the server
node dist/index.js config.json
# List available tools
node dist/index.js config.json discover_tools
License
This MCP server is licensed under the MIT License.
Created by Third Strand Studio
FAQ
- What is the Tool Chainer MCP server?
- Tool Chainer is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Tool Chainer?
- This profile displays 10 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
Ratings
4.5★★★★★10 reviews- ★★★★★Shikha Mishra· Oct 10, 2024
Tool Chainer is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Piyush G· Sep 9, 2024
We evaluated Tool Chainer against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Chaitanya Patil· Aug 8, 2024
Useful MCP listing: Tool Chainer is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Sakshi Patil· Jul 7, 2024
Tool Chainer reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Ganesh Mohane· Jun 6, 2024
I recommend Tool Chainer for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Oshnikdeep· May 5, 2024
Strong directory entry: Tool Chainer surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Dhruvi Jain· Apr 4, 2024
Tool Chainer has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Rahul Santra· Mar 3, 2024
According to our notes, Tool Chainer benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Pratham Ware· Feb 2, 2024
We wired Tool Chainer into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Yash Thakker· Jan 1, 2024
Tool Chainer is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.