Skip to main content
Glama
themudhaxk

mudbase-mcp-server

by themudhaxk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mudbase-mcp-server

No user-submitted related servers found.

    Related Servers

    • workspace-mcp

      MarcoCaamal
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to safely read, write, edit, search, and optionally run commands within one or more named project workspaces, while maintaining a work journal and tracking changes.
      19
      MIT

    • remus-mcp

      christianmz565
      A
      license
      C
      quality
      B
      maintenance
      Enables interaction with REMUS Jet databases through the MCP protocol, supporting local stdio and remote HTTP/SSE transports for database operations and project management.
      20
      AGPL 3.0

    • Runar

      muhammadluth
      A
      license
      B
      quality
      C
      maintenance
      Provides AI agents with durable, searchable project memory, session notes, skills, and bounded context packs over MCP while leaving orchestration to the client.
      15
      MIT

    • Demo Database MCP

      PhoenixCo-Founder
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables database querying and modification through an MCP server where each action is gated by human-granted scopes, per-call confirmations for destructive operations, and revocable access.
      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 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pairing: documents, collections, buckets, and files are cleanly separated. Even similar tools like list_documents and search_documents are distinguished by structured filtering versus full-text search.

    Naming Consistency5/5

    All tools follow a consistent mudbase_<verb>_<noun> pattern in snake_case, making the API predictable. The only compound name, get_file_download_url, still follows the same get_<resource>_<aspect> convention.

    Tool Count5/5

    14 tools is well within the ideal range and each tool covers a distinct operation across two coherent domains: document CRUD/search and file storage. No tool feels redundant or unnecessary.

    Completeness4/5

    Document CRUD, listing, filtering, and search are covered, along with file upload/list/get/delete and signed download URLs. Minor gaps exist around collection lifecycle management and file metadata updates, but agents can accomplish the core workflows without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources