Skip to main content
Glama
ed-smartass

esmole-mcp

by ed-smartass
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to esmole-mcp

No user-submitted related servers found.

    Related Servers

    • elastic-security-mcp

      AndreuCrespo
      A
      license
      Not graded
      quality
      D
      maintenance
      A Python MCP server that provides AI agents with a controlled, read-first interface to Elasticsearch, Kibana Security, Fleet, and Elastic Defend.
      MIT

    • Elasticsearch MCP Server

      maestra-io
      A
      license
      Not graded
      quality
      F
      maintenance
      A read-only MCP server for Elasticsearch 7.10 clusters, providing tools for cluster info, health, index listing, and Query DSL search with Google OAuth and Bearer token authentication.
      2 npm
      MIT

    • Elasticsearch 7.x MCP Server

      imlewc
      A
      license
      C
      quality
      D
      maintenance
      Provides an MCP protocol interface for interacting with Elasticsearch 7.x databases, supporting comprehensive search functionality including aggregations, highlighting, and sorting.
      3
      11
      Apache 2.0

    • elasticsearch-logs

      ws135y
      F
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server for Elasticsearch log querying. Enables natural language search, filtering, context retrieval, and aggregation of logs.
      -
    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.7/5.0

    Scored across 10 tools

    Disambiguation4/5

    The connection group (add/list/update/remove/test) is crisply separated, and the ES group mostly targets distinct facets (search, indices, mapping, health). The main overlap is es_request, a generic passthrough that can duplicate every specialized ES tool, but the descriptions frame it explicitly as the escape hatch and the others as convenience wrappers.

    Naming Consistency4/5

    Connection tools follow a clean verb_noun pattern, and the ES tools are consistently namespaced with an es_ prefix that clearly separates the two domains. Minor deviation: es_cluster_health is noun-only while es_list_indices and es_get_mapping include verbs, so ordering is not perfectly uniform.

    Tool Count5/5

    Ten tools is well within the sweet spot, split sensibly between five connection-management operations and five ES query operations. Each tool covers a distinct need and no obvious padding is present.

    Completeness4/5

    Connection lifecycle is fully covered (add, list, update, remove, test) with good detail on scopes and secrets. The ES side covers search, indices, mapping, and health, while document-level and index-level CRUD (get/put doc, create/delete index) exist only via the generic es_request escape hatch, which is workable but less discoverable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources