@chrismichaelps / pudu-lang-mcp
Model Context Protocol server for Pudu language documentation and compiler tools
0.1.1Apache-2.01
InstallClose
Use @chrismichaelps/pudu-lang-mcp
Install this release
From your project, run:
pudu install @chrismichaelps/pudu-lang-mcp@0.1.1An exact version can install a new release immediately. Without a version, pudu follows the 72-hour minimum release age for new resolutions.
pudu install @chrismichaelps/pudu-lang-mcpThen import it
import PuduLangMcp as PuduLangMcpTo contribute
git clone https://github.com/chrismichaelps/pudu-lang-mcp
Compiler.md
Compiler tools
type: module path: "@root/src/PuduLangMcp/App/Tools/Compiler.pudu" fidelity: Active domain: "[[domain/Tool]]" grammar: "[[grammar/pudu]]" depth_score: 0.5 depth_status: MODERATE coupling: 5 interface_stability: 0.8 tags: [module] aliases: [Compiler Tools]
Purpose
pudu_check, pudu_format, pudu_lint, pudu_run, and pudu_test: the compiler's own answers for a piece of code or a workspace file.
Interface
Signatures
export fn check(context: &Context.Context, args: &Arguments.Args) -> Result[Str, ToolError.ToolFailure]
export fn format(context: &Context.Context, args: &Arguments.Args) -> Result[Str, ToolError.ToolFailure]
export fn lint(context: &Context.Context, args: &Arguments.Args) -> Result[Str, ToolError.ToolFailure]
export fn run(context: &Context.Context, args: &Arguments.Args) -> Result[Str, ToolError.ToolFailure]
export fn test(context: &Context.Context, args: &Arguments.Args) -> Result[Str, ToolError.ToolFailure]Linkage
- Requires: [[src/PuduLangMcp/App/Context]], [[src/PuduLangMcp/Services/Workspace]], [[src/PuduLangMcp/Services/Toolchain]], [[src/PuduLangMcp/Domain/Catalog/Arguments]], [[src/PuduLangMcp/Utils/TextBounds]], [[src/PuduLangMcp/Constants/Server]].
- Consumed by: [[src/PuduLangMcp/App/Tools/Registry]].
Algorithm
Every command runs through onTarget: with no compiler, ToolchainMissing; otherwise [[src/PuduLangMcp/Services/Workspace]] withTarget places the code, and the command runs in the target's directory on the file's path relative to it. Output is the command's standard output then its standard error, trimmed, with the scratch directory's path removed, bounded to DOC_CHARS.
| Tool | Command | Answer |
|---|---|---|
pudu_check | check <file> | the compiler's report, "no diagnostics" included |
pudu_format | fmt --stdout <file> | the formatted code; on failure "The code could not be formatted:" and the diagnostics |
pudu_lint | lint <file> | the findings, or the linter's clean report |
pudu_run | run --confined <file> | exit status N, then output; a stopped run says it was stopped after the deadline |
pudu_test | test [path] in the workspace root | the test report |
pudu_run and pudu_test use timeoutMs (default RUN_TIMEOUT_MS); the others COMMAND_TIMEOUT_MS. pudu_test's path, when given, must resolve inside the workspace.
Negative Logic (Prohibited Paths)
- A non-zero exit is an answer, not a tool failure ([[decisions/ADR-0005-text-tool-results]]).
pudu_runnever runs without--confined.
Edge Cases
- A command stopped at its deadline answers its partial output after a line saying so.
Depth
DEPTH 0.5.
Grill Log
- Q: Run
pudu_testconfined? A: No; the project's suites are its own code, written to touch files and processes. The tool's annotations say so instead.
Referenced by
[[src/PuduLangMcp/App/Tools/_MOC]]