sysknife
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | No | Anthropic API key for the planner. Optional: with no provider key SysKnife falls back to Ollama. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sysknife_audit_verifyA | Verify the tamper-evident Ed25519-signed hash chain over the audit log. Returns status (intact/broken/cannot_verify), rows_checked, and, on broken, the first offending row. Read-only and safe to call without prior sysknife_plan. |
| sysknife_doctorA | Diagnose SysKnife: pings the daemon, reports the configured brain provider/model, the audit DB path, and a quick audit-chain status (intact/broken/unknown). Read-only and safe to call without prior sysknife_plan. |
| sysknife_executeA | Execute exact steps produced by sysknife_plan. Every step requires a one-time receipt from an explicit |
| sysknife_historyA | List past SysKnife audit-log entries. Read-only and safe to call without prior sysknife_plan. Filters: status (succeeded/failed/canceled/...), action (canonical action name), since (UTC RFC 3339 timestamp), limit (default 20). Returns a list of HistoryEntry rows. |
| sysknife_planA | Plan a Linux system administration intent. Returns typed steps with risk levels, resolved commands, and daemon transaction IDs. IMPORTANT: Present the plan, then STOP. The user must run |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| about | Discovery resource for Codex and other MCP clients. |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: plan creates plans, execute runs approved steps, history lists audit entries, audit_verify checks chain integrity, and doctor diagnoses daemon state. There is no meaningful overlap or ambiguity among the five.
All tools share the sysknife_ prefix and use lower_snake_case, which gives a strong predictable brand. However, sysknife_history and sysknife_doctor are noun-style names relative to the verb-style execute, plan, and audit_verify, creating a minor convention inconsistency.
Five tools is a well-scoped size for this server's purpose. Each tool covers a distinct phase of the plan-execute-audit lifecycle without redundancy or bloat.
The tool surface covers the full intended workflow: planning, executing approved steps, viewing history, verifying audit integrity, and running diagnostics. The approval step is intentionally external to MCP, so there is no missing in-band operation that would create a dead end.