Skip to main content
Glama
Wasim-Shaikh25

splunk-dashboard-mcp

by Wasim-Shaikh25
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to splunk-dashboard-mcp

No user-submitted related servers found.

    Related Servers

    • Splunk MCP Server

      datamann119
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables users to interact with Splunk instances to execute SPL queries, manage saved searches, and monitor system health. It provides a clean interface for listing dashboards, indexes, and logs through the Model Context Protocol.
      221 npm
      -

    • R1 Dash Master

      alekm
      F
      license
      Not graded
      quality
      C
      maintenance
      Builds importable RUCKUS One Data Studio dashboards from a declarative spec, enabling users to create valid dashboards without learning Superset internals or guessing field names.
      2
      -

    • Splunk MCP Server

      rootiq-ai
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Splunk Enterprise and Splunk Cloud instances through standardized MCP interface. Supports executing SPL queries, managing indexes and saved searches, listing applications, and retrieving server information with flexible authentication options.
      -

    • mcp-server-splunk

      pahar0
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to search, manage, and analyze data in Splunk instances through the Model Context Protocol. Supports SPL queries, index management, alerts, dashboards, and more.
      55 PyPI
      1
      Apache 2.0

    • Splunk SOAR MCP Server

      Ewiges-M
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to operate a Splunk SOAR instance headlessly via its REST API, supporting container triage, playbook authoring and execution, and asset management.
      2
      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 17 tools

    Disambiguation4/5

    Most tools map cleanly to distinct resources and actions (dashboards, reports, alerts, auth, docs, query). The only mild overlap is get_dashboard already including a can_write flag while check_dashboard_access exists as a separate pre-check tool.

    Naming Consistency4/5

    The set follows a clear verb_noun pattern for the main resources (list_dashboards, get_dashboard, create_report, update_alert). A few outliers like splunk_login, splunk_docs, whoami, and query_splunk break the pattern but are still recognizable.

    Tool Count4/5

    17 tools is on the heavier side but justifiable given three resources (dashboards, reports, alerts) plus auth, query, and docs. Each tool has a clear role, though the count is at the upper edge of ideal.

    Completeness3/5

    Core lifecycle is covered for dashboards, reports, and alerts (list/get/create/update), but there are no delete tools for any resource, and sharing/permission management is only checkable, not settable. Search is present but saved search lifecycle lacks deletion or duplication.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources