CyberChef API MCP Server ✨🧑🍳
If you already use CyberChef API, the cyberchef api mcp server is the piece that lets your assistant work with it directly. CyberChef API MCP Server ✨🧑🍳.
This model context protocol (MCP) server interfaces with the CyberChef Server API. Allowing you to use any LLM/MCP client of your choosing to utilise the tools and resources within CyberChef.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
get_cyberchef_operations_categories — resource - gets updated Cyber Chef categories for additional context / selection of the correct operationsget_cyberchef_operation_by_category — resource - gets list of Cyber Chef operations for a selected categorybake_recipe — tool - bake (execute) a recipe (a list of operations) in order to derive an outcome from the input databatch_bake_recipe — tool - bake (execute) a recipe (a list of operations) in order to derive an outcome from a batch of input dataperform_magic_operation — tool - perform CyberChef's magic operation which is designed to automatically detect how your data is encoded and which operations can be used toConfiguration is passed through the environment: CYBERCHEF_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. CyberChef API's toolset — get_cyberchef_operations_categories, get_cyberchef_operation_by_category, bake_recipe and 2 more — is a fair guide to whether it matches your workflow. It is maintained by slouchd; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| get_cyberchef_operations_categories | __resource__ - gets updated Cyber Chef categories for additional context / selection of the correct operations |
| get_cyberchef_operation_by_category | __resource__ - gets list of Cyber Chef operations for a selected category |
| bake_recipe | __tool__ - bake (execute) a recipe (a list of operations) in order to derive an outcome from the input data |
| batch_bake_recipe | __tool__ - bake (execute) a recipe (a list of operations) in order to derive an outcome from a batch of input data |
| perform_magic_operation | __tool__ - perform CyberChef's magic operation which is designed to automatically detect how your data is encoded and which operations can be used to decode it |
| Variable | Description | Required |
|---|---|---|
| CYBERCHEF_API_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.