Skip to main content
Glama
PCfVW

mcp-arangodb-async

by PCfVW
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-arangodb-async

No user-submitted related servers found.

    Related Servers

    • mcp-arango-mind

      woolkingx
      A
      license
      B
      quality
      D
      maintenance
      Turns ArangoDB into a schema-driven MCP server for agents, enabling search-describe-exec workflows for database, graph, and knowledge operations without oversizing the tool list.
      10
      MIT

    • mcp-server-db

      Nam088
      A
      license
      B
      quality
      B
      maintenance
      A universal MCP server enabling AI assistants to query and manage six database engines (Postgres, Redis, Elasticsearch, MySQL, MongoDB, LDAP) through 113+ tools with read-only safety and fault tolerance.
      100
      11 npm
      82
      MIT

    • MySQL MCP Server

      SaadRiaz99
      A
      license
      Not graded
      quality
      B
      maintenance
      Production-ready MCP server for MySQL databases enabling AI assistants to interact with MySQL through secure, validated, and audited tools.
      2
      MIT

    • GraphRAG TypeScript MCP Tools

      Akakinad
      F
      license
      C
      quality
      C
      maintenance
      An MCP server that connects AI assistants to a Neo4j graph database, enabling querying of movie data through tools like graph statistics, genre-based search, and movie details, along with advanced features such as LLM sampling and completions.
      4
      -
    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

    B3/5.0

    Scored across 46 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but several aliases (e.g., arango_add_vertex as alias for arango_insert, arango_graph_traversal as alias for arango_traverse) create potential confusion, as an agent may select the wrong tool if unaware of the alias.

    Naming Consistency4/5

    The majority of tools follow a consistent arango_verb_noun pattern. However, minor inconsistencies exist, such as mixing 'add' and 'create' (e.g., arango_add_edge vs arango_create_collection) and using noun_noun for arango_query_builder.

    Tool Count2/5

    With 46 tools, the server has significantly more than the ideal range. While the domain is broad, many tools are workflow management or backup-related, and the presence of aliases adds redundancy, making tool selection more complex.

    Completeness4/5

    The tool set covers a wide range of ArangoDB operations including CRUD, graph management, indexing, schema validation, querying, backup/restore, and multi-tenancy. Minor gaps like lack of transaction support are acceptable for an MCP server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources