Skip to main content
Glama
elephant-xyz

Elephant MCP Server

by elephant-xyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Elephant MCP Server

No user-submitted related servers found.

    Related Servers

    • ObjectStack MCP Server by objectstack-ai

      ObjectStack MCP Serverofficial

      objectstack-ai
      A
      license
      Not graded
      quality
      D
      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
    • Elasticsearch MCP Server by elastic

      Elasticsearch MCP Serverofficial

      elastic
      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
      2,662 npm
      719
      Apache 2.0

    • code-grapher

      mufasadb
      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
      -

    • Graph-Memory

      stevepridemore
      A
      license
      A
      quality
      B
      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
      105 npm
      2
      MIT

    • Baby-SkyNet

      spie-mkroehn
      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
      -
    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 10 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: listing vs. getting specific Atlas properties, dataset info, schema access, lexicon queries, and script search. There is no overlap or ambiguity between the tools.

    Naming Consistency5/5

    All tool names follow a consistent camelCase verb_noun pattern (list, get, query) with clear resource nouns, making it easy to predict behavior from names.

    Tool Count5/5

    The 10 tools cover the read-only data access and lexicon schema domain without redundancy. The count is well within the ideal range for a focused server.

    Completeness5/5

    The surface covers the core workflows: listing datasets/counties, inspecting schemas, running queries, and retrieving lexicon details. The read-only nature is clearly communicated, and no critical operations are missing for the apparent purpose.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources