TransformerBee.MCP

Name: TransformerBee.MCP
Author: Hochfrequenz

@Hochfrequenz

Repository

About TransformerBee.MCP

MCP server wrapper around transformer.bee aka edifact-bo4e-converter

#mcp #transformer #edifact #energiewirtschaft #fastmcp

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "TransformerBee.mcp": {
      "command": "docker",
      "args": [
        "pull",
        "ghcr.io/hochfrequenz/transformerbee.mcp:latest"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is TransformerBee.MCP?

TransformerBee.MCP is a proof‑of‑concept Model Context Protocol (MCP) server that wraps transformer.bee, a tool for converting EDIFACT BO4E messages to the German EDI@Energy standard. It is written in Python and relies on the python-mcp SDK and the transformerbeeclient.py library. The server is intended for developers integrating energy‑sector message transformations into MCP‑compatible applications like Claude Desktop.

How to use TransformerBee.MCP?

Install the package via pip install transformerbeemcp or uv install transformerbeemcp, or pull the Docker image ghcr.io/hochfrequenz/transformerbee.mcp:latest. Start the server with the CLI command run-transformerbee-mcp-server (when installed as a package) or via Docker. Configure the required environment variables (TRANSFORMERBEE_HOST, optionally TRANSFORMERBEE_CLIENT_ID and TRANSFORMERBEE_CLIENT_SECRET) to point to a running transformer.bee instance. Register the server in Claude Desktop by editing claude_desktop_config.json or using fastmcp install server.py from the repo root.

Key features of TransformerBee.MCP

MCP server wrapping the transformer.bee converter.
Installable as Python package or Docker container.
CLI entry point for easy startup.
Environment‑variable configuration for host and credentials.
Pre‑configured for integration with Claude Desktop.
Built on python-mcp and transformerbeeclient.py.

Use cases of TransformerBee.MCP

Convert EDIFACT BO4E messages to EDI@Energy inside an MCP ecosystem.
Automate energy‑data transformation via Claude Desktop or other MCP hosts.
Test transformer.bee functionality without writing direct client code.
Embed message conversion in AI‑assisted workflow pipelines.

FAQ from TransformerBee.MCP

What does TransformerBee.MCP actually do?

It is an MCP server that exposes the transformer.bee library (a converter for EDIFACT BO4E to EDI@Energy) through the Model Context Protocol, allowing MCP‑compatible AI assistants to perform message transformations.

What dependencies does TransformerBee.MCP require?

The server depends on python-mcp (MCP SDK) and transformerbeeclient.py (client for transformer.bee). A running instance of transformer.bee must be accessible (typically at http://localhost:5021).

Where does the actual data transformation happen?

All transformation logic runs on the transformer.bee instance configured via the TRANSFORMERBEE_HOST environment variable. The MCP server does not perform conversions itself; it relays requests and responses.

What transports and authentication does TransformerBee.MCP support?

The MCP server uses standard STDIO transport (typical for MCP). Authentication to transformer.bee is managed through optional TRANSFORMERBEE_CLIENT_ID and TRANSFORMERBEE_CLIENT_SECRET environment variables, as documented in the transformerbeeclient.py library.