m5c MCP server
m5c mcp serve exposes local, offline package authoring tools to MCP-compatible agents. Use it when an agent needs typed access to package guidance, validation, tests, lowering, import previews, and reports.
The MCP server is for local development. It does not apply bundles to a live Mach5 server.
Start the server
m5c mcp serve
Configure your agent to launch the command over stdio.
Tooling model
The server provides typed tools for common local workflows:
| Tool | Purpose |
|---|---|
m5c_guide | Return package authoring guidance for topics such as contracts, modules, mappings, detections, imports, and troubleshooting. |
m5c_validate | Validate a local workspace or package and return structured diagnostics. |
m5c_test | Run conformance, mapping, fixture, and expected-finding tests. |
m5c_build | Build a deterministic local package artifact. |
m5c_lower | Lower a package to generated bundle resources and reports. |
m5c_import_sigma | Preview/export Sigma rules as Detection IR plus diagnostics. |
m5c_read_report | Read generated reports for review. |
m5c_app_check | Run an app-oriented local package check and return next-step guidance. |
Recommended agent loop
- Ask for package guidance.
- Validate the workspace.
- Run tests.
- Lower the package.
- Inspect generated reports.
- Validate and apply bundles separately with explicit credentials and namespace.
Example prompt for an agent:
Use the m5c MCP tools. Start with m5c_guide(topic="package-workflow"), then run validation, tests, and lower the package. Do not apply bundles.
Safety boundaries
- MCP tools operate on local package source and local generated output.
- Live bundle apply is not exposed through the local MCP server.
- Do not place secrets in package source.
- Review generated resources and reports before deployment.