Skip to main content
Glama
EverdredIIDX

Splunkbase MCP Server

by EverdredIIDX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SPLUNKBASE_PASSWORDYesYour Splunkbase password (stored in plaintext)
SPLUNKBASE_USERNAMEYesYour Splunkbase username

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchB
Search Splunkbase for apps.

Args:
    query: The search query to search Splunkbase for

Returns:
    A list of results from the search
get_app_latest_versionA
Get the latest compatible version of an app for a specific Splunk version.

Args:
    app: The name or numeric ID of the Splunkbase app
    splunk_version: The Splunk version to check compatibility with
    is_cloud: Whether to check compatibility with Splunk Cloud

Returns:
    Dictionary containing release information
download_appB
Download a specific version of an app. If no version is specified, downloads the latest.

Args:
    app: The name or numeric ID of the Splunkbase app
    output_dir: Directory to save the downloaded app
    version: Optional specific version to download

Returns:
    Success message with download details

Prompts

Interactive templates invoked by user choice

NameDescription
app_compatibility_checkCreate a prompt for checking app compatibility.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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.3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: download_app downloads files, get_app_latest_version retrieves version information, and search finds apps. The descriptions reinforce these distinct functions, making misselection unlikely.

Naming Consistency4/5

Two tools follow a consistent verb_noun pattern (download_app, get_app_latest_version), but 'search' deviates by using only a verb without a noun. This minor inconsistency slightly reduces predictability, though the names remain readable and intuitive.

Tool Count3/5

With only 3 tools, the server feels thin for a Splunkbase integration, as it lacks operations like installing apps, managing updates, or accessing app details. While the tools cover basic search and download workflows, the scope is limited and may require agents to work around gaps.

Completeness2/5

The tool set is severely incomplete for a Splunkbase server, missing core operations such as installing downloaded apps, listing installed apps, updating apps, or retrieving detailed app metadata. Agents will face dead ends when trying to perform common Splunkbase management tasks beyond basic search and download.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources