Chepy MCP Service (CyberChef like Python library)
LocalAbout Chepy MCP Service (CyberChef like Python library)
Chepy MCP Service exposes Chepy data-transformation operations through an MCP server for developers and data-analysis workflows. Its single `bake` tool runs Chepy recipes as pipelines, while a resource lists operations and signatures.
Key features
- 01Chain operations with the `bake` tool
- 02Use Chepy recipe JSON
- 03Discover operations and signatures
- 04Return text or Base64-encoded binary
- 05Recipe compatibility with Chepy CLI
Use cases
- 01Encode or decode data in a pipeline
- 02Apply multiple Chepy transformations to input
- 03Inspect available operations and parameters
MCP support
The server exposes the `bake` tool for running Chepy operation pipelines and the `resource://chepy_operations` resource for discovering operations, signatures, and descriptions.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEchepy-mcp
MCP Service for Chepy Library Functions
Overview
This project exposes the powerful Chepy data transformation library as an MCP (Model Context Protocol) server. It allows you to access Chepy's tools (like encoding, decoding, and data manipulation) via a single flexible API: the bake pipeline tool, inspired by CyberChef.
Features
- Single pipeline tool (
bake): Chain one or more Chepy operations, each with parameters, in a single request - Chepy recipe JSON format: Pipelines are described using Chepy's own recipe serialization, making them compatible with Chepy's import/export and CLI tools
- Resource endpoint: Discover all available Chepy operations and their signatures
- Unittest-based test suite for robust validation
Installation
-
Install uv if it is not installed yet.
$ curl -LsSf https://astral.sh/uv/install.sh | sh -
Clone the repository:
git clone https://github.com/nebucaz/chepy-mcp.git cd chepy-mcp -
Install dependencies:
uv sync
Run
Run the server with:
$ uv run src/server.py
Usage
The Chepy Recipe JSON Format
The bake tool expects a pipeline in the Chepy recipe JSON format:
{
"input": "hello world",
"recipe": [
{"function": "to_base64", "args": {}},
{"function": "from_base64", "args": {}}
]
}
- Each step in the
recipelist is an object with afunction(the Chepy operation name) andargs(a dictionary of arguments for that function). - This format is fully compatible with Chepy's own recipe import/export and CLI tools.
The response will indicate if the output is text or binary:
{
"type": "text",
"data": "hello world"
}
Discover Available Operations
Fetch the resource endpoint to get all available Chepy operations, their parameter signatures, and descriptions:
- Resource URI:
resource://chepy_operations
Example response:
{
"to_base64": {
"signature": "(alphabet: str = 'standard')",
"description": "Encode the input string to base64"
},
"from_base64": {
"signature": "(alphabet: str = 'standard', remove_non_alpha: bool = True)",
"description": "Decode base64 encoded string"
}
}
Extending
- All Chepy operations are available through the pipeline tool; no need to add individual wrappers.
- Add more tests in the
tests/directory as needed.
Notes
- The
baketool will automatically detect if the output is text or binary and encode binary as base64. - For a list of valid operations and their parameters, see the
resource://chepy_operationsresource. - Only the
baketool and the Chepy operations resource are exposed for maximum flexibility and maintainability. - The pipeline format is fully compatible with Chepy's own recipe serialization and CLI tools.
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.