Blaze MCPs Makers

We design, build, and evolve Model Context Protocol servers for any ecosystem

Since 2004 Blaze has shipped custom back‑end platforms in e‑commerce, fintech, health‑tech, and IoT. Now we bring that full‑stack experience to MCP: the open protocol that feeds real‑time context to large language models. Whether you need a green‑field MCP server, a bridge for legacy ERP data, or developer tooling around HexaMCP, Blaze is the team that builds it.

View on GitHub Get start

What we build

Tailor‑made MCP servers

Purpose‑built to match your domain models, data flows, and security policies.

Connector engineering

We craft adapters for databases, SaaS apps, message queues, proprietary hardware—anything with a protocol.

Developer SDKs & CLIs

Typed SDKs for Python, Node, Go, and Rust, plus a one‑line tunnel CLI for instant secure testing.

Workflow orchestration

Built‑in schedulers, retry logic, and streaming transforms keep context fresh without brittle cron jobs.

Observability & QA

Grafana dashboards, OpenTelemetry traces, and contract tests so you see every message that reaches your LLM.

Training & co‑dev

We upskill your engineers and embed alongside them until hand‑off.

Versatile Across Stacks

Blaze speaks Python · Node.js · Rust · Go · Java · .NET · Elixir and more. Mono‑repo or poly‑repo, microservices or monolith—our patterns adapt to your architecture.

Python
Node.js
Rust
Go
Java
.NET
Elixir
Mono-repo Poly-repo Microservices Monolith

Hosting is optional

Need us to run it? We can. Prefer on‑prem? No problem. Blaze’s DevOps group provisions repeatable IaC (Terraform/Ansible) for your VPC, then hands the keys to your SRE team. Cloud, edge, or air‑gapped datacenter—same code, same support.

Ready Connectors (Always Expanding)

  • # 1. WordPress / WooCommerce
  • # 2. Odoo ERP (v13–v17)
  • # 3. HubSpot CRM & CMS
  • # 4. Finvasia Shoonya API
  • # 5. Zabbix Monitoring

New connector in under 72 hours with plugin architecture.

Connectors Illustration

Configuration of

HexaMCP server

Code

 
{
  "Your MCP project name": {
    "type": "sse",
    "url": "http://localhost:3000",
  }
}

Code

 
{
  "Your MCP project name": {
    "type": "stdio",
    "command": "node",
    "args": [
       "--directory",
       "Path to odoo-mcp",
       "run",
       "server.py"
    ],
    "env": {
      "ODOO_URL": "{}",
      "ODOO_DB": "{}",
      "ODOO_USER": "{}",
      "ODOO_API_KEY": "{}",
    }
  }
}

Code

 
{  
    "hexamcpServers": { 
    "hexamcp-rag-web-browser": { 
        "command": "npx",
        "args": [ "-y", "@hexa/mcp-server-rag-web-browser" ], 
        "env": { "HEXAMCP_API_TOKEN": "{{apiToken@string::Your HexaMCP API token}}"  
            } 
        } 
    } 
}

Code

 
{
  "sites": [
    {
      "id": "site1",
      "name": "My WordPress Site",
      "url": "https://example.com",
      "consumerKey": "XXXX XXXX XXXX XXXX XXXX XXXX",
      "consumerSecret": "XXXX XXXX XXXX XXXX XXXX XXXX",
      "username": "admin",
      "applicationPassword": "XXXX XXXX XXXX XXXX XXXX XXXX",

    }
  ],
  "activeSite": "site1"
}

Code

 
ZABBIX_API_URL=https://your-zabbix-server/api_jsonrpc.php
ZABBIX_USER=your_zabbix_username
ZABBIX_TOKEN=your_zabbix_api_token

Code

 
{
  "servers": {
    "my-mcp-server-38b534a9": {
      "type": "stdio",
      "command": "node",
      "args": [
        "/your/folder/path/mcp-hubspot/build/index.js"
      ]
    }
  }
}

Launch in

Just minutes

  • # 1. Download the BlazeMCP client for your platform eg: apple silicon wget https://downloads.hexamcp.com/mac/arm/hexamcp
  • # 2. Make it executable chmod +x hexamcp
  • # 3. Login ./hexamcp login you@your_email.com
  • # 4. Run your MCP server through HexaMCP ./hexamcp -c "your-mcp-server-start-command" -e ENV1=ENV_VARIABLE1 -e ENV2=ENV_VARIABLE2

Choose your OS and get the HexaMCP client in one click.

macOS
Windows
Linux

Takes care of networking, security, and routing so you can stay focused on building your MCP apps.

Coming soon

Your own persistent URL

Reserve a unique subdomain (e.g., yourname.srv.hexamcp.com) for consistent and professional access.

FAQ

Frequently asked questions

Model Context Protocol is an open standard for streaming structured context—documents, SQL rows, live telemetry—to large language models via HTTP/SSE/WebSocket.

HexaMCP is Blaze’s own open‑source reference implementation of the Model Context Protocol, maintained by our engineering team. Blaze MCP projects build on HexaMCP with production‑grade security, role‑based access control, multi‑tenant sharding, an ever‑expanding connector library, and a polished developer UX. Blaze layers on production security, role‑based access control, multi‑tenant sharding, connector library, observability, and a polished developer UX.

Typical first release ships in **2-3 weeks**, including critical connectors and CI/CD setup.

Yes—grab our Starter kit (open source) and use the tunnel CLI with 50 K messages/month at no cost.

Absolutely. We run 2‑day and 5‑day workshops covering MCP architecture, connector design, and LLM prompting patterns.

Core libraries live at github.com/Blaze‑Open/MCP and all ready‑made connectors live at github.com/HexaMCP/ — both under Apache 2.0. Proprietary add‑ons remain yours under project‑based licensing.

Book a 15‑minute discovery call or email [email protected]. Tell us what you want your LLM to know—Blaze will make the context flow.

Ready to integration support with HexaMCP?

Be part of the movement shaping the future of connectivity with the MCP

View on GitHub

Lets Discuss