Skip to main content
Glama
niels-emmer

dendrite-admin-mcp

by niels-emmer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to dendrite-admin-mcp

No user-submitted related servers found.

    Related Servers

    • matrix-mcp-server

      guan-tends
      A
      license
      Not graded
      quality
      A
      maintenance
      A standalone MCP tool server that exposes Matrix chat operations as callable tools, enabling messaging, room management, user management, and ID resolution for MCP-compatible clients.
      66 npm
      MIT

    • litellm-mcp

      nikitatsym
      A
      license
      A
      quality
      A
      maintenance
      MCP server for the LiteLLM proxy, enabling agents to administer resources like keys, teams, users, models, and proxy settings through risk-graded meta-tools.
      6
      MIT

    • llmstudio-mcp

      dam2452
      F
      license
      A
      quality
      C
      maintenance
      MCP server that connects LLM agents to a local LM Studio instance, enabling model management, OpenAI-compatible chat completions, text completions, and embeddings through a set of tools.
      9
      1
      -

    • agentforge

      doggychip
      F
      license
      A
      quality
      F
      maintenance
      MCP server that exposes 300+ AI agents as tools via a single API key. Supports listing agents, invoking any agent with chat-completion style messages, checking agent health, and retrieving platform statistics.
      5
      3
      -

    • litellm-mcp

      weeebdev
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides tools to interact with the LiteLLM proxy API, enabling LLM completions, embeddings, image generation, and admin operations.
      11 npm
      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.9/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a specific administrative action: registration tokens have clear CRUD separation (list/get/create/update/delete), while room operations (evacuate, purge, download state) and user operations (register, reset password, whois) are distinct. Even similar-sounding tools like evacuate_room and evacuate_user are clearly differentiated by their target resource.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (list_registration_tokens, create_registration_token, reset_password, etc.). Minor deviations include 'whois' (a single word) and 'fulltext_reindex' (which could be interpreted as reindex_fulltext), but these are still understandable and do not create confusion.

    Tool Count5/5

    With 15 tools, the set is well-scoped for a Matrix homeserver admin tool. Each tool addresses a distinct administrative need (token management, user admin, room admin, server maintenance) and none feel redundant. The count is at the upper boundary but remains justified.

    Completeness3/5

    The tool set covers registration token CRUD, core user operations (create, reset password, whois), and room management (evacuate, purge, download state), but notable gaps exist: there is no user deletion/deactivation, no list users tool, and no general room listing/search. Agents cannot perform the full lifecycle for users or rooms.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources