AnythingLLM Control Plane MCP Server
Related Servers
Alternatives to AnythingLLM Control Plane MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables MCP-compatible clients to interact with AnythingLLM, providing tools for workspace management, chat and thread operations, document operations, vector search, and system inspection.346MIT
- FlicenseCqualityDmaintenanceMCP server for AnythingLLM that enables AI document chat platform interaction with tools for workspaces, chat, documents, threads, and system operations.17-
- AlicenseBqualityDmaintenanceEnables seamless integration with AnythingLLM instances, providing complete workspace management, chat operations, document handling, user administration, and AI agent configuration through natural language.3828 npm16MIT
- AlicenseNot gradedqualityCmaintenanceEnables AnythingLLM to be controlled by any MCP-compatible client via HTTP, SSE, or WebSocket, with automatic workspace selection and background operation.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents and users to manage workspace files, monitor system metrics, take persistent notes, and retrieve weather data via MCP tools and resources.-
- AlicenseAqualityBmaintenanceEnables MCP-capable agents to create and invoke OpenServerless endpoints, manage secrets, and configure integrations such as S3, PostgreSQL, Redis, Milvus, and MongoDB.13Apache 2.0
TDQS
Scored across 5 tools
Each tool targets a distinct resource and action: workspace CRUD operations (list/create/delete) are clearly separated from system environment and vector count queries. No two tools have overlapping purposes, making selection unambiguous.
All tool names follow a consistent verb_noun pattern in snake_case: list_workspaces, create_workspace, delete_workspace, get_system_env, get_vector_count. The verbs and nouns are predictable and match the action/resource pair.
Five tools is well-scoped for a control plane server, covering core workspace management and system information without unnecessary bloat. The count feels appropriate for the apparent domain.
The workspace lifecycle is incomplete: create, list, and delete exist, but update is missing. System environment is read-only, and there is no way to modify configuration. These gaps are notable for a control plane server, though the core viewing/deleting operations are present.