Skip to main content
Glama
jbowensii

anythingllm-mcp

by jbowensii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to anythingllm-mcp

No user-submitted related servers found.

    Related Servers

    • AnythingLLM MCP Server

      andreperez
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP-compatible clients to interact with AnythingLLM, providing tools for workspace management, chat and thread operations, document operations, vector search, and system inspection.
      34
      6
      MIT

    • anythingllm-mcp

      DezGDNY
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to search and ask questions about documents stored in AnythingLLM workspaces through MCP tools.
      4
      MIT

    • anythingllm-mcp

      moliver28
      F
      license
      C
      quality
      D
      maintenance
      MCP server for AnythingLLM that enables AI document chat platform interaction with tools for workspaces, chat, documents, threads, and system operations.
      17
      -

    • MSIM

      giancbaring
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AnythingLLM to be controlled by any MCP-compatible client via HTTP, SSE, or WebSocket, with automatic workspace selection and background operation.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool maps to a distinct resource+action: the ask_workspace/get_answer pair forms a clear async job pattern, and workspace CRUD (list/get/create/update/delete) is unambiguous. The only mild overlap is embedded documents appearing in get_workspace vs list_documents, but descriptions clearly differentiate them.

    Naming Consistency5/5

    All names follow a clean verb_noun pattern (list_workspaces, get_workspace, create_workspace, update_workspace, delete_workspace, list_documents, update_embeddings, ask_workspace, get_answer). No convention mixing or vague verbs.

    Tool Count5/5

    Nine tools is well-scoped for an AnythingLLM management server, with each tool earning its place across workspace management, chat, and embeddings.

    Completeness4/5

    Workspace lifecycle is fully covered (list/get/create/update/delete) and the chat flow has a complete async request+poll pair. The one notable gap is document ingestion—there is no tool to create/upload documents, only to list them and attach/remove existing ones, so new content must be added externally.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources