Azu Toolkit MCP

A native Crystal MCP server for coding assistants working with Azu, Azu CLI, CQL, JoobQ, JoobQ Pro, Authly, Session, and Schema.

Inspect version-matched source, preview generators, run trusted development checks, read redacted telemetry, and review supported operational changes. Runs locally over stdio; no hosted service or Node runtime is required.

Preview: the server and coordinated CLI/core changes need to be installed together. Production adapters require CQL's apply_reviewed and JoobQ's redrive_reviewed; older versions fail closed. See validation for what has actually been exercised.

Build

Requires Crystal 1.22.1+, Shards, SQLite development headers, OpenSSL and libyaml.

shards install
shards build --release
./bin/azu-mcp --version

Create a user-owned configuration outside your project:

# ~/.config/azu-mcp/config.yml
workspaces:
  store:
    root: /absolute/path/to/store
    trusted: false

azu-mcp check --config ~/.config/azu-mcp/config.yml
azu-mcp serve --config ~/.config/azu-mcp/config.yml

serve reserves stdout for MCP. Connect it through your client's configuration; it is not an interactive console.

Start here

• Configuration and trust
• VS Code, Codex and Claude Code
• Tools and workflows
• Telemetry
• Reviewed operations
• Architecture
• Validation and limits

Example requests:

Explain this project's endpoint, model and job boundaries using its installed versions.

Preview a live Product scaffold, show conflicts, then build it after approval.

Find evidence for slow requests and repeated SQL in the retained telemetry.

echo, flux, dashforge, duo, topia, joobqui, and authority are not supported integrations. They may appear in dependency metadata, but are not indexed as dedicated toolkit repositories.

Development

shards build
AZU_MCP_EXECUTABLE="$PWD/bin/azu-mcp" crystal spec
crystal tool format --check src spec
python3 scripts/check_docs.py

See architecture for the SDK adapter and validation for protocol, application and soak checks. Package publication and client UI validation are separate release gates; documentation does not imply they have happened.