mcpField
M
MCP Toolbox

MCP Toolbox

Local
github.com/tollbitDeveloper Tools0Updated 62w ago
Repository

About MCP Toolbox

MCP Toolbox is a stdio bridge for MCP clients to access tools hosted by Tollbit’s Dynamic Toolbox. It uses API-key authentication and can target a selected toolbox.

Key features

  1. 01stdio bridge for MCP tools
  2. 02Fetches and calls cloud-hosted tools
  3. 03API-key authentication
  4. 04Optional toolbox selection
  5. 05Claude Desktop configuration helper

Use cases

  1. 01Connect an MCP client to Tollbit-hosted tools
  2. 02Add the server to Claude Desktop
  3. 03Switch between toolboxes for different tool sets

MCP support

It exposes Tollbit Dynamic Toolbox tools to stdio-based MCP clients by proxying tool listing and calls to the hosted server.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "toolbox": {
      "command": "npx",
      "args": [
        "-y",
        "@tollbit/mcp-toolbox"
      ]
    }
  }
}
Run commandnpx -y @tollbit/mcp-toolbox

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@tollbit/mcp-toolbox

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

MCP Toolbox

Docs GitHub Discord

A stdio Model Context Protocol (MCP) server that bridges Tollbit's Dynamic Toolbox to stdio-based MCP clients.

Why Use This?
  • Plug-and-play for MCP clients: Works out-of-the-box with clients that expect stdio MCP servers (e.g., Claude Desktop).
  • Dynamic tools from the cloud: Tools are fetched and executed via Tollbit’s backend; nothing to install locally.
  • Simple and secure: Authenticate with an API key and optionally target a specific toolbox with --toolbox-id.
Installation

No install required to run:

npx @tollbit/mcp-toolbox --api-key <your_api_key>
Quick Start
  • Run the bridge locally (any MCP stdio client):
npx @tollbit/mcp-toolbox --api-key <your_api_key> [--toolbox-id <id>]

Optional host override:

TB_MCP_HOST=https://mcp.tollbit.dev/ npx @tollbit/mcp-toolbox --api-key <your_api_key>
  • Claude Desktop (macOS) one-liner:
npx -y @tollbit/mcp-toolbox install_claude --api-key <your_api_key> [--toolbox-id <id>]

This adds @tollbit/mcp-toolbox to Claude Desktop's claude_desktop_config.json with your API key.

Key Features
  • Stdio MCP bridge that proxies tools/list and tools/call to Tollbit's dynamic server.
  • Claude-safe tool names: Sanitizes tool names to alphanumeric/underscore for compatibility.
  • Streaming HTTP transport with API key auth.
  • Keep-alive and graceful shutdown for reliability.
  • macOS installer for Claude Desktop configuration.
CLI Options
  • --api-key (required): Your Tollbit API key (get it from the developer portal).
  • --toolbox-id (optional): ID of the toolbox to use. Defaults to mcp.
Environment Variables
  • TB_MCP_HOST (optional): Base URL for the dynamic MCP server. Default: https://mcp.tollbit.dev/
Documentation
Common Use Cases
  • Claude Desktop integration: Quickly add a dynamic MCP server using the install_claude script.
  • Custom MCP client bridge: Use as a stdio server process to access Tollbit-hosted tools.
  • Multi-toolbox workflows: Switch contexts with --toolbox-id to test or target different tool sets.
Requirements
  • Node.js: 18+ recommended (ESM, top-level import support).
  • macOS: Required only for the install_claude helper script.
  • Tollbit API key: Obtain from the developer portal at https://hack.tollb.it/
  • Network access to TB_MCP_HOST (default https://mcp.tollbit.dev/).
Support
License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.