Functions (also called MCP servers on Blaxel Console) represent custom code that can be executed by passing specific input arguments. They are lightweight programs that expose specific capabilities (accessing databases, APIs, local files, etc.) through the standardized Model Context Protocol (MCP). MCP servers are designed to equip agents with tools to interact with the world. When an agent runs on Blaxel, the function in the MCP server is run separately from the action model and agent logic. This ensures not only minimal latency for your consumers as well as optimal resource utilization, but also better design practice for your agentic system.

When deployed on Blaxel, MCP servers are hosted on Global Agentics Network, a high-availability and low-latency compute infrastructure. You only provide the code, and Blaxel automates its hosting, execution and scaling - providing you with one single global endpoint to access the MCP server.

​
MCP hosting on Blaxel

Blaxel has a purpose-built implementation for MCP transport that uses WebSockets protocol instead of Server-Sent Events (SSE) or stdio to feature robust capabilities — including persistent connections with automatic reconnection handling, multi-tenant support, health monitoring, and seamless AI framework integration.

At this time, MCP servers deployed on Blaxel are only hosted server-side and cannot be installed locally. Only WebSockets protocol is supported.

For developers interested in the technical details, our implementation is available open-source through Blaxel’s Supergateway and Blaxel’s SDK.

There are two routes you can take when hosting MCPs on Blaxel:

  • Use one of the pre-built MCP servers from the Blaxel Store
  • Deploy a custom MCP server from your code

Develop an MCP server

Read our guide for developing a custom MCP server with Blaxel.

Host an MCP server on Blaxel

Read our guide for deploying your custom MCP server on Blaxel.

Invoke functions

Learn how to run invocation requests on your function.

Was this page helpful?