Skip to main content
AnythingLLM speaks MCP through the standard mcpServers JSON convention (the Claude-Desktop shape) — its MCP docs show where the servers file lives for your install (desktop vs Docker). The binary comes first: brew install supernovae-st/tap/nika (other paths). Wiring is manual — nika wire has no AnythingLLM target. Add the nika entry to AnythingLLM’s MCP servers file: 
{ "mcpServers": { "nika": { "command": "nika", "args": ["mcp"] } } }
The stable contract is the stanza — nika + mcp, stdio. If AnythingLLM’s documented file location has moved, the stanza still applies.

​
What you get

Validation, explanation, schema and cost answers for .nika.yaml workflows — no execution, no mutation, by design (the oracle’s contract). Running workflows stays on the terminal, where the budget flags and traces live.

​
Verify

AnythingLLM’s agent-skills / MCP panel lists nika with the eight nika_* tools. Then prove the loop end-to-end: integrate in 10 minutes.