Skip to main content
Glama
elephant-xyz

Elephant MCP Server

by elephant-xyz

Related Servers

Alternatives to Elephant MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects Claude Code to any ObjectStack deployment, enabling discovery, querying, and updating of objects and records, plus running business actions, all under user permissions and row-level security.
      Apache 2.0
    • A
      license
      B
      quality
      D
      maintenance
      Connects Claude and other MCP clients to Elasticsearch data, allowing users to interact with their Elasticsearch indices through natural language conversations.
      3
      1,413
      711
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to intelligently analyze and query codebases using knowledge graphs, supporting natural language code search, relationship discovery, and incremental updates.
      11
      -
    • A
      license
      A
      quality
      C
      maintenance
      Self-hosted personal knowledge graph for Claude that persists across sessions, devices, and tools. Built on Neo4j with local semantic embeddings; OAuth 2.1 lets Claude Code, Claude Desktop, and claude.ai web all hit the same graph.
      23
      67
      2
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides Claude AI with persistent, searchable memory management across sessions using SQL database, semantic analysis with multi-provider LLM support (Anthropic/Ollama), vector search via ChromaDB, and graph-based knowledge relationships through Neo4j integration.
      1
      -

    TDQS

    A3.6/5.0

    Scored across 22 tools

    Disambiguation3/5

    Most tools have distinct purposes, but several names collide across subdomains: getPropertySchema (Elephant schema) vs getPropertyQuerySchema (county query table), and listPropertiesByClassName vs listOracleProperties. The detailed descriptions help, but an agent could easily misroute these calls.

    Naming Consistency4/5

    The server mostly follows a predictable snake_case verb-noun pattern, with consistent query/schema pairs like queryProperties/getPropertyQuerySchema and queryPermits/getPermitQuerySchema. A few deviations such as getVerifiedScriptExamples and the overloaded getProperty* prefix slightly weaken the pattern, but naming is still largely predictable.

    Tool Count3/5

    With 22 tools, the server sits in the heavy range and spans several related subdomains: schema metadata, property data, permits, places, and colocation analysis. Each tool has a real purpose, but the surface could reasonably be pruned or split without losing capability.

    Completeness4/5

    The tool set covers discovery, schema introspection, data retrieval, query execution, coverage qualification, and advanced analytics across the main entities. Minor gaps exist, such as no direct address/owner search beyond SQL and no place-detail-by-ID operation, but these are workable through existing tools.

    Maintenance

    ActivityActive
    ResponsivenessNo issues