In this article
AnythingLLM Desktop starts MCP through Agent Skills or @agent, requires host commands, and supports Tools rather than every MCP primitive.
AnythingLLM Desktop MCP failures should be split into server startup, tool availability, and model invocation. The application does not start every configured MCP server at launch, and a configured command must actually exist on the host computer.
The concrete application boundary
The Desktop documentation states that MCP servers start when Agent Skills is opened or the @agent directive is invoked, rather than automatically at application boot. An anythingllm.autoStart: false setting requires a manual start. The integration loads Tools; Resources, Prompts, and Sampling are not supported by this documented path. This matters when a server is compatible with the protocol but exposes the wrong primitive for the expected task. Desktop also does not install an arbitrary command named in the MCP configuration. The host must provide the executable through PATH or an explicit binary path. A working language model says nothing about that host dependency (AnythingLLM Desktop MCP guide).
A practical route
Open Agent Skills and inspect the server card and status. The configuration lives at plugins/anythingllm_mcp_servers.json within the AnythingLLM storage directory, with entries under mcpServers. Check the configured command against the actual host installation. If a GUI process has a different PATH from your terminal, use the documented executable location rather than assuming the terminal’s successful command proves GUI availability. Click Refresh to reload configuration and restart MCP servers, or use the selected server’s gear menu Start action for a manual start.
A worked example
A read-only note tool is configured with a command launcher that is absent from the host’s application environment. The model answers ordinary questions, but the server card reports failure. Correct the actual command availability, refresh Agent Skills, and verify the tool appears before asking @agent to read a fictional note. Keep the input path harmless and inspect the returned content.
| Check | Record |
|---|---|
| Startup | The Agent Skills server status after loading or manual Start. |
| Dependency | The installed host executable and the configuration command pointing to it. |
| Invocation | The exposed Tool and its observed result for the fictional note. |
Reading the failure correctly
If the server runs and the Tool is visible but the model never calls it, investigate model capability and task context after startup is proven. If the requested capability is a Resource or Prompt rather than a Tool, changing PATH cannot make it supported. Desktop application logs provide another observation point for process startup failures (AnythingLLM Desktop overview) (AnythingLLM language model guide).
What completes the check
The correction should identify the failed stage, not merely make the status card disappear. Removing an MCP entry and removing its separately installed host tool are also different actions; Desktop configuration cleanup does not imply host dependency cleanup.
Related background: llama.cpp server: a local API from a GGUF model, VRAM for LLMs: why model size is only part of the calculation.