Skip to main content
Glama
moliver28

anythingllm-mcp

by moliver28

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ANYTHING_LLM_BASENoBase URL for AnythingLLM API (default: http://localhost:3001/api/v1)http://localhost:3001/api/v1
ANYTHING_LLM_API_KEYYesYour AnythingLLM API key

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_tokenA

Validate the current API token

generate_api_keyB

Generate a new API key (admin)

list_workspacesB

List all workspaces

get_workspaceB

Get details of a specific workspace

create_workspaceC

Create a new workspace

update_workspaceD

Update workspace settings

delete_workspaceC

Delete a workspace

chatC

Send a chat message to a workspace (mode: chat or query)

stream_chatC

Stream a chat message to a workspace

upload_documentC

Upload a document to a workspace

update_embeddingsC

Add or remove documents from workspace embeddings

list_workspace_documentsC

List all documents in a workspace

list_threadsC

List all threads in a workspace

get_threadC

Get details of a specific thread

delete_threadC

Delete a thread from a workspace

get_system_envB

Get system environment configuration

openai_chat_completionC

OpenAI-compatible chat completion endpoint (use workspace as model)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.9/5.0

Scored across 17 tools

Disambiguation5/5

All tools target distinct operations: chat, workspace, thread, document, and admin functions. Chat variants (chat, stream_chat, openai_chat_completion) differ by mode, and workspace/thread/document tools have clear boundaries.

Naming Consistency4/5

Most tools follow verb_noun pattern in snake_case (e.g., create_workspace, list_threads). A few like 'chat' and 'openai_chat_completion' deviate slightly, but overall naming is predictable.

Tool Count5/5

17 tools cover workspace, document, thread, chat, and admin operations without feeling excessive. The scope matches the server's purpose well.

Completeness4/5

CRUD operations are present for workspaces and threads (though thread creation is implicit via chat). Document management includes upload, listing, and embedding updates. Missing explicit delete document but covered via update_embeddings.

Maintenance

ActivityInactive
ResponsivenessNo issues