BoltMCP MCP Server

The MCP server the BoltMCP Helm chart deploys into the customer's own Kubernetes cluster. Customers define their own servers and tools through the BoltMCP dashboard, so the tool surface is tenant-defined rather than a fixed public catalog. The chart derives the public hostname from global.domain and the ingress documentation names server. as the externally routed host; agents and MCP clients connect there over HTTP, authenticating against the deployment's OIDC provider.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/boltmcp-mcp-server"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
aid: boltmcp-mcp-server
name: BoltMCP MCP Server
description: The MCP server the BoltMCP Helm chart deploys into the customer's own Kubernetes cluster.
  Customers define their own servers and tools through the BoltMCP dashboard, so the tool surface is tenant-defined
  rather than a fixed public catalog. The chart derives the public hostname from global.domain and the
  ingress documentation names server.<domain> as the externally routed host; agents and MCP clients connect
  there over HTTP, authenticating against the deployment's OIDC provider.
humanURL: https://install.boltmcp.io/docs/architecture
image: https://www.boltmcp.io/boltmcp-logo/icon/icon-mark-light-original.png
baseURL: https://server.{global.domain}/
tags:
- MCP
- Agents
- Self-Hosted
tags_raw:
- Model Context Protocol
- Agents
- Self-Hosted
properties:
- type: MCPServer
  url: mcp/boltmcp-mcp.yml
- type: Documentation
  url: https://install.boltmcp.io/docs/ingress-tls