MCPHub Lab
MCPHub LabRegistryboltmcp
boltmcp

boltmcp

Built by boltmcp • 337 stars

Visit Repository

What is boltmcp?

No description available

How to use boltmcp?

1. Install a compatible MCP client (like Claude Desktop). 2. Open your configuration settings. 3. Add boltmcp using the following command: npx @modelcontextprotocol/boltmcp 4. Restart the client and verify the new tools are active.
🛡️ Scoped (Restricted)
npx @modelcontextprotocol/boltmcp --scope restricted
🔓 Unrestricted Access
npx @modelcontextprotocol/boltmcp

Key Features

Native MCP Protocol Support
Real-time Tool Activation & Execution
Verified High-performance Implementation
Secure Resource & Context Handling

Optimized Use Cases

Extending AI models with custom local capabilities
Automating system workflows via natural language
Connecting external data sources to LLM context windows

boltmcp FAQ

Q

Is boltmcp safe?

Yes, boltmcp follows the standardized Model Context Protocol security patterns and only executes tools with explicit user-granted permissions.

Q

Is boltmcp up to date?

boltmcp is currently active in the registry with 337 stars on GitHub, indicating its reliability and community support.

Q

Are there any limits for boltmcp?

Usage limits depend on the specific implementation of the MCP server and your system resources. Refer to the official documentation below for technical details.

Official Documentation

View on GitHub

BoltMCP

BoltMCP is an enterprise-grade MCP orchestration platform to create, deploy, and manage custom MCP servers on-premises.

<!-- ## Demo Video demo of creating and using an MCP server -->

Installation

There are two ways to install and run BoltMCP:

Testing locally with Docker Compose

To take a quick spin on your laptop, install BoltMCP with Docker Compose. This isn’t suitable for production.

Deploying to production with Helm

To deploy to a Kubernetes cluster, install BoltMCP with Helm. This is suitable for enterprise production environments.

For followers of OpenMCP

OpenMCP was an early exploration of techniques in token-management for MCP servers. Since then we’ve spent a lot of time building secure servers and learning from the process, which has evolved the project into what is now called BoltMCP. Thank you for your support and experimentation with OpenMCP, we hope this enthusiasm continues with all the developments we’ve made for this iteration.

What has changed

Hosting

  • All software is now self-hosted on-premises
  • Enterprise-grade cloud native infrastructure and integrations

Transport & authorization

  • All servers are Streamable HTTP by default
  • All servers are secured with OAuth 2 by default
  • Each server can now interact with multiple upstream APIs with different auth requirements

Rich customization

  • You can spin up custom MCP servers on-the-fly with a subset of tools tailored for your specific use-case
  • Tools can now be fully customized with rich transformation of inputs/outputs, and composition of multiple API operations within a single tool, all backed by a declarative json/yaml spec.
  • Tools can be registered up-front, retrieved on demand, or partially registered and lazy-loaded on demand

MCP client playground

  • The application now bundles with an MCP client playground which you can use to chat with your servers
  • The official MCP Inspector is also bundled with the application

Bring your own LLM

  • Configure an LLM of your choice, self-hosted or cloud, to use for the AI-powered features within the application, including the playground

Global Ranking

-
Trust ScoreMCPHub Index

Based on codebase health & activity.

Manual Config

{ "mcpServers": { "boltmcp": { "command": "npx", "args": ["boltmcp"] } } }