AnythingLLM Control Plane MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANYTHINGLLM_API_KEY | No | Developer API Key for authentication. Required if authentication is enabled in AnythingLLM. | |
| ANYTHINGLLM_BASE_URL | No | Base URL of the AnythingLLM API. | http://localhost:3001/api/v1 |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workspacesA | List all workspaces in AnythingLLM. Returns: JSON string containing the list of workspaces or error status. |
| create_workspaceB | Create a new workspace in AnythingLLM. Args: name: Name for the new workspace. Returns: JSON string with created workspace details or error message. |
| delete_workspaceB | Delete a workspace in AnythingLLM by slug. Args: slug: The workspace slug to delete. Returns: JSON string or status message confirming deletion or reporting error. |
| get_system_envA | Retrieve system environment and configuration dump from AnythingLLM Admin API. Returns: JSON string containing system environment variables and configuration. |
| get_vector_countA | Get vector count for AnythingLLM (system-wide or workspace-specific). Args: slug: Optional workspace slug. If provided, returns vector count for that workspace. Returns: JSON string or status message with vector count stats. |
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 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.