AnythingLLM MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANYTHINGLLM_API_KEY | No | Your AnythingLLM API key (obtain from your AnythingLLM instance at /settings/api-keys) | |
| ANYTHINGLLM_BASE_URL | No | Your AnythingLLM instance URL | http://localhost: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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| initialize_anythingllmC | Initialize the AnythingLLM client with API credentials |
| list_workspacesB | List all available workspaces in AnythingLLM |
| get_workspaceC | Get details of a specific workspace |
| create_workspaceC | Create a new workspace |
| update_workspaceC | Update an existing workspace |
| delete_workspaceC | Delete a workspace |
| chat_with_workspaceC | Send a chat message to a workspace |
| list_documentsB | List all documents in a workspace |
| delete_documentC | Delete a document from a workspace |
| get_system_settingsC | Get system settings |
| update_system_settingsC | Update system settings |
| list_usersB | List all users in the system |
| create_userC | Create a new user |
| update_userC | Update an existing user |
| delete_userC | Delete a user |
| list_api_keysB | List all API keys |
| create_api_keyC | Create a new API key |
| delete_api_keyC | Delete an API key |
| embed_textC | Embed text directly into a workspace |
| embed_webpageC | Embed a webpage into a workspace |
| get_chat_historyC | Get chat history for a workspace |
| clear_chat_historyC | Clear all chat history for a workspace |
| get_system_infoC | Get general system information |
| get_system_statsC | Get system statistics |
| list_llm_providersB | List available LLM providers |
| update_llm_providerC | Update LLM provider configuration |
| get_vector_database_infoC | Get vector database configuration |
| update_vector_databaseC | Update vector database configuration |
| get_workspace_settingsC | Get settings for a specific workspace |
| update_workspace_settingsC | Update settings for a specific workspace |
| process_document_urlC | Process a document from a URL |
| get_document_vectorsC | Get vector embeddings for a document |
| search_workspaceC | Search within a workspace |
| list_agentsB | List all available agents |
| create_agentC | Create a new agent |
| update_agentC | Update an existing agent |
| delete_agentC | Delete an agent |
| invoke_agentC | Invoke an agent with input |
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 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.