Skip to main content
Glama
Sign In
orazionelson

existdb-mcp

by orazionelson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to existdb-mcp

No user-submitted related servers found.

    Related Servers

    • fontem-mcp-server by fontem-eu

      fontem-mcp-serverofficial

      fontem-eu
      A
      license
      Not graded
      quality
      B
      maintenance
      A Model Context Protocol server that surfaces Fontem entities and queries to Claude via standard MCP tools.
      Apache 2.0

    • scrivener-mcp

      nazaryanenko
      A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server that connects Claude Desktop to Scrivener writing projects, enabling project overviews, searches, chapter reading, word counts, synopses, and notes access.
      11
      MIT

    • Nabu

      arvicco
      A
      license
      Not graded
      quality
      A
      maintenance
      Self-hosted read-only MCP server over a local library of ancient-text corpora — 2.47M documents and 118M passages from 258 sources (cuneiform, Classical, biblical, medieval and more), with the license class tracked on every passage. 14 research tools: full-text search, concordance, passage display, dictionary definitions, etymologies, cognates, parallel passages, text alignment, place lookup etc
      2
      MIT

    • RLM Knowledge Base

      cgaeking
      A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that enables Claude Desktop to search and read local documents via full-text and fuzzy search, providing direct access to indexed files without chunking.
      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.8/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: documentation lookup, namespace listing, searching, and data operations are separated without overlap. Even the two list tools differ by scope (functions in a namespace vs. all namespaces), and delete_resource explicitly covers both documents and collections.

    Naming Consistency5/5

    All tool names follow the pattern 'existdb_<verb>_<object>' using snake_case, with verbs like lookup, list, search, get, execute, validate, store, delete, and create. This uniform convention makes the tool set predictable and easy to navigate.

    Tool Count5/5

    With 12 tools, the server is well-scoped for an eXist-db MCP, covering both documentation lookup and essential XML database operations. The count is appropriate and neither too sparse nor bloated.

    Completeness5/5

    The tool set provides comprehensive coverage of the eXist-db domain: documentation (lookup, list, search, snippets) and data management (create collection, store/get/list documents, delete, execute/validate XQuery). Store_document handles both create and replace, covering update operations without needing a separate tool.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources