AnythingLLM MCP Server
Related Servers
Alternatives to AnythingLLM MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables async chat with AnythingLLM workspaces so slow local-model answers never trip the ~60s MCP tool-call timeout, plus full workspace management (list, get, create, update, delete), document listing, and embedding updates over the AnythingLLM REST API.9MIT
- AlicenseAqualityBmaintenanceEnables managing and controlling AnythingLLM instances through MCP, providing tools to list, create, and delete workspaces, retrieve system environment settings, and get vector counts.51MIT
- AlicenseAqualityBmaintenanceEnables MCP-compatible clients to interact with AnythingLLM, providing tools for workspace management, chat and thread operations, document operations, vector search, and system inspection.346MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to search and ask questions about documents stored in AnythingLLM workspaces through MCP tools.4MIT
- AlicenseAqualityCmaintenanceEnables interaction with an Airbyte instance through natural language, supporting workspaces, sources, destinations, connections, jobs, logs, tags, streams, and connector definitions.3677 PyPI5Apache 2.0
- AlicenseNot gradedqualityDmaintenanceConnects AnythingLLM to Coolify for natural language management of self-hosted infrastructure, including diagnostics, log fetching, and deployment automation.MIT
TDQS
Scored across 38 tools
Most tools have distinct purposes targeting specific resources (e.g., workspaces, agents, users) and actions (CRUD operations). However, some potential overlap exists between workspace/document embedding tools (embed_text, embed_webpage, process_document_url) and between various 'get_' information tools (system_info, system_stats, vector_database_info), which could cause minor confusion.
Tool names follow a highly consistent verb_noun pattern throughout, using snake_case exclusively. Examples include create_workspace, delete_user, update_agent, list_documents, get_system_info, and embed_text. This predictability makes the toolset easy to navigate and understand.
With 38 tools, the count feels heavy for a single server, bordering on excessive. While the domain (AnythingLLM management) is broad, many tools could potentially be consolidated (e.g., multiple embedding methods) or grouped into subservers. This may overwhelm agents with choice complexity.
The toolset provides comprehensive coverage for the AnythingLLM domain, including full CRUD operations for core resources (workspaces, agents, users, documents), system configuration (settings, LLM providers, vector database), workspace interactions (chat, search, embedding), and administrative functions. No obvious gaps are present for the stated purpose.