Skip to main content
Glama
spron-in

mcp-everest

by spron-in
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EVEREST_HOSTNoEverest API base URL.http://localhost:8080
EVEREST_API_KEYYesYour Percona Everest API key (JWT token).
EVEREST_TIMEOUTNoRequest timeout in seconds.30
EVEREST_READONLYNoRead-only mode flag.false
EVEREST_VERIFY_SSLNoSSL verification flag.true

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
list_database_clustersB

List available database clusters in the specified namespace.

get_database_clusterC

Get details of a specific database cluster.

get_database_cluster_credentialsC

Get credentials for a specific database cluster.

get_database_cluster_componentsC

Get components of a specific database cluster.

create_database_clusterA

Create a new database cluster in the specified namespace.

Args:
    namespace: The namespace to create the cluster in
    name: Name of the database cluster
    engine_type: Type of database engine (e.g. 'pxc')
    storage_size: Size of storage using the Mi, Gi suffix
    replicas: Number of database replicas
    cpu: CPU cores per replica
    memory: Memory per replica using the Mi, Gi suffix
    allow_unsafe: Allow unsafe configurations
    proxy_replicas: Number of proxy replicas

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

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

Scored across 5 tools

Disambiguation5/5

Each tool has a clear, distinct purpose: create, get details, get components, get credentials, and list. No two tools overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_database_cluster pattern in snake_case, with predictable suffixes like _components and _credentials for specific sub-features.

Tool Count5/5

Five tools is well-suited for managing database clusters, covering core operations without being excessive or insufficient.

Completeness3/5

The set covers create and read operations (get, list, components, credentials) but lacks update and delete tools, leaving a notable gap in full lifecycle management.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources