anythingllm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANYTHINGLLM_API_KEY | Yes | Your AnythingLLM Developer API key (Settings -> Tools -> Developer API) | |
| ANYTHINGLLM_BASE_URL | Yes | The base URL of your AnythingLLM instance (e.g. http://your-anythingllm-host:3001) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_workspaceA | Async chat query to an AnythingLLM workspace. Returns a job_id instantly so the call never hits the ~60s MCP timeout (use for slow models like Qwen 32B). Poll get_answer until status is 'done'. |
| get_answerA | Fetch an ask_workspace job by job_id: status pending|done|error, plus answer text and source document titles when done. |
| list_workspacesA | List all AnythingLLM workspaces (slug, name, chatModel, chatMode, topN). |
| get_workspaceB | Get one workspace's full settings (prompt, model, mode, topN, threshold) and embedded documents. |
| update_workspaceC | Update a workspace's settings. settings is an object, e.g. {openAiPrompt, openAiTemp, chatMode, topN, similarityThreshold, chatModel, chatProvider, queryRefusalResponse}. |
| create_workspaceC | Create a new workspace by name (AnythingLLM derives the slug). |
| delete_workspaceA | Delete a workspace by slug. DESTRUCTIVE -- removes the workspace and its embeddings. |
| list_documentsA | List documents known to the AnythingLLM system (the document/vector file tree under localFiles). |
| update_embeddingsB | Add or remove documents in a workspace's embeddings. adds/deletes are arrays of document paths from list_documents/get_workspace. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool maps to a distinct resource+action: the ask_workspace/get_answer pair forms a clear async job pattern, and workspace CRUD (list/get/create/update/delete) is unambiguous. The only mild overlap is embedded documents appearing in get_workspace vs list_documents, but descriptions clearly differentiate them.
All names follow a clean verb_noun pattern (list_workspaces, get_workspace, create_workspace, update_workspace, delete_workspace, list_documents, update_embeddings, ask_workspace, get_answer). No convention mixing or vague verbs.
Nine tools is well-scoped for an AnythingLLM management server, with each tool earning its place across workspace management, chat, and embeddings.
Workspace lifecycle is fully covered (list/get/create/update/delete) and the chat flow has a complete async request+poll pair. The one notable gap is document ingestion—there is no tool to create/upload documents, only to list them and attach/remove existing ones, so new content must be added externally.