Install the Mélodium MCP Server

The Mélodium MCP server gives an AI assistant live access to Mélodium program validation, standard library reference lookup, the language guide, and a full CI/CD migration guide, on top of what the skill already teaches it. It’s a full reference on its own: even a client that can’t load the skill gets the same material, plus the ability to check a program file for errors and look up the exact signature of a treatment or function as it writes your pipeline.

It is published as the melodium-mcp crate, with source in the melodium-mcp directory of the Mélodium repository. It reuses the same loading code as melodium check and melodium info, so its answers match what the CLI would report, and it validates programs in mock mode: reading the file being checked is the only I/O it performs.

Tools It Exposes

check_program: parse and validate a Mélodium program file (.mel, Compo.toml, or .jeu), returning structured errors and the list of available entrypoints.
get_program_info: describe each entrypoint of a program file: identifier, documentation, and parameters.
list_library_elements: list standard library treatments, functions, models, contexts, and data types, optionally filtered by area (e.g. std/flow, http) and/or kind.
describe_element: full signature of one standard library element by identifier (e.g. std/flow::emit): documentation, generics, parameters, and, for treatments, inputs, outputs, required models and contexts.
search_reference: keyword search across standard library identifiers and documentation.
get_language_guide: Mélodium’s dataflow execution model explained for an AI reading or writing Mélodium code, treatments, tracks, models, contexts, connections, generics, and project layout.
get_cicd_migration_guide: a full reference for migrating a GitHub Actions or GitLab CI pipeline to a Mélodium cicd project, or for building one from scratch.
search_book / read_book_chapter: keyword search and full content of the Mélodium book ’s chapters.

Install It

Building the binary, putting it on PATH, and registering it with Claude Code, Claude Desktop, Cursor, Codex CLI, or any other MCP-compatible client is covered in the MCP server installation guide .

Going Further

With the MCP server connected, ask the AI to validate what it writes as it goes, for example “check this program with the MCP server before showing it to me”, “look up the signature of std/flow::emit”, or “use the CI/CD migration guide to convert this GitHub Actions workflow” or “…this GitLab CI pipeline”. The guide names those two directly, but its concepts (steps, artifacts, triggers, parallelism) carry over just as well to migrating from Jenkins, CircleCI, or any other CI/CD system. Combine it with the skill and the pipeline-building workflow for the most reliable results.

Advanced Implementation Install the Mélodium Skill