Cloud Native MCP Server

Kubernetes Service

Mon, 01 Jan 0001 00:00:00 +0000

Kubernetes Service#

The Kubernetes service provides comprehensive container orchestration and resource management capabilities with 28 specialized tools for managing your Kubernetes clusters.

Overview#

The Kubernetes service in Cloud Native MCP Server enables AI assistants to manage Kubernetes resources efficiently. It provides tools for deployments, services, configmaps, secrets, and other core Kubernetes resources.

Key Capabilities#

### 🔧 Deployment Management Complete control over Kubernetes deployments including creation, updates, scaling, and deletion operations.

### 🗂️ Resource Management Manage all Kubernetes resources including pods, services, configmaps, secrets, and persistent volumes.

### 📊 Monitoring Get detailed information about pods, nodes, and resource usage across your cluster.

### 🔐 Security Manage secrets, RBAC configurations, and other security-related Kubernetes resources.

Available Tools (28)#

Pod Management#

kubernetes-get-pods: Get detailed information about pods in a namespace
kubernetes-list-pods: List all pods in a namespace
kubernetes-get-pod: Get specific pod details
kubernetes-delete-pod: Delete a specific pod
kubernetes-get-pod-logs: Get logs from a pod
kubernetes-get-pod-events: Get events related to a pod

Deployment Management#

kubernetes-list-deployments: List all deployments in a namespace
kubernetes-get-deployment: Get specific deployment details
kubernetes-create-deployment: Create a new deployment
kubernetes-update-deployment: Update an existing deployment
kubernetes-delete-deployment: Delete a deployment
kubernetes-scale-deployment: Scale a deployment
kubernetes-restart-deployment: Restart a deployment

Service Management#

kubernetes-list-services: List all services in a namespace
kubernetes-get-service: Get specific service details
kubernetes-create-service: Create a new service
kubernetes-update-service: Update an existing service
kubernetes-delete-service: Delete a service

Configuration Management#

kubernetes-list-configmaps: List all configmaps in a namespace
kubernetes-get-configmap: Get specific configmap details
kubernetes-create-configmap: Create a new configmap
kubernetes-update-configmap: Update an existing configmap
kubernetes-delete-configmap: Delete a configmap
kubernetes-list-secrets: List all secrets in a namespace
kubernetes-get-secret: Get specific secret details
kubernetes-create-secret: Create a new secret
kubernetes-update-secret: Update an existing secret
kubernetes-delete-secret: Delete a secret

Quick Examples#

List all pods in default namespace#

1
2
3
4
5
6
7
8
9


{
 "method": "tools/call",
 "params": {
 "name": "kubernetes-list-pods",
 "arguments": {
 "namespace": "default"
 }
 }
}

Get specific deployment details#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10


{
 "method": "tools/call",
 "params": {
 "name": "kubernetes-get-deployment",
 "arguments": {
 "name": "my-app",
 "namespace": "production"
 }
 }
}

Create a new configmap#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13


{
 "method": "tools/call",
 "params": {
 "name": "kubernetes-create-configmap",
 "arguments": {
 "name": "app-config",
 "namespace": "default",
 "data": {
 "config.json": "{\"debug\": true, \"port\": 8080}"
 }
 }
 }
}

Best Practices#

Always specify namespaces when working with Kubernetes resources
Use labels and annotations effectively for resource organization
Implement proper RBAC policies for security
Monitor resource usage to optimize cluster performance
Regularly backup critical configurations

Next Steps#

Helm Service for package management
Configuration Guides for detailed setup
Security Best Practices for securing your cluster

Helm Service

Mon, 01 Jan 0001 00:00:00 +0000

Helm Service#

The Helm service provides comprehensive package management and deployment capabilities with 31 tools for managing Helm charts, releases, and repositories.

Overview#

The Helm service in Cloud Native MCP Server enables AI assistants to manage Helm charts and releases efficiently. It provides tools for chart installation, upgrades, rollbacks, and repository management.

Key Capabilities#

### 📦 Chart Management Complete control over Helm charts including installation, upgrading, and uninstalling releases.

### 🗄️ Repository Management Manage Helm chart repositories with tools for adding, updating, and searching charts.

### 🔄 Release Management Handle Helm releases with rollback, history, and status checking capabilities.

### ⚙️ Configuration Manage chart values, configurations, and dependencies effectively.

Available Tools (31)#

Chart Management#

helm-list-releases: List all releases in all namespaces
helm-install-chart: Install a chart
helm-upgrade-release: Upgrade a release
helm-uninstall-release: Uninstall a release
helm-get-release: Get information about a release
helm-rollback-release: Rollback a release
helm-get-history: Get release history
helm-search-repo: Search for charts in the repository
helm-add-repo: Add a chart repository
helm-update-repo: Update chart repositories
helm-repo-list: List chart repositories
helm-get-values: Get values for a release
helm-template: Template a chart locally
helm-package: Package a chart directory into a chart archive
helm-pull: Download a chart from a repository
helm-push: Push a chart to a registry

Chart Information#

helm-get-chart: Get information about a chart
helm-create: Create a new chart
helm-dependency-build: Build out the charts dependencies
helm-dependency-update: Update the charts dependencies
helm-lint: Examine a chart for possible issues
helm-test: Run tests for a release
helm-status: Show the status of a release
helm-history: Show the history of a release
helm-get-manifest: Show the manifest for a release
helm-get-notes: Show the notes for a release
helm-get-hooks: Show the hooks for a release
helm-get-all: Get all resources for a release
helm-verify: Verify the provenance of a chart
helm-show-chart: Show information about a chart
helm-show-readme: Show the README of a chart

Quick Examples#

Install a chart#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12


{
 "method": "tools/call",
 "params": {
 "name": "helm-install-chart",
 "arguments": {
 "chart": "nginx-ingress",
 "repo": "https://kubernetes.github.io/ingress-nginx",
 "release": "my-nginx",
 "namespace": "ingress-nginx"
 }
 }
}

Upgrade a release#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14


{
 "method": "tools/call",
 "params": {
 "name": "helm-upgrade-release",
 "arguments": {
 "release": "my-nginx",
 "chart": "nginx-ingress",
 "repo": "https://kubernetes.github.io/ingress-nginx",
 "set_values": {
 "controller.replicaCount": 3
 }
 }
 }
}

List all releases#

1
2
3
4
5
6
7


{
 "method": "tools/call",
 "params": {
 "name": "helm-list-releases",
 "arguments": {}
 }
}

Best Practices#

Always specify namespaces when installing Helm charts
Use values files for complex configurations
Regularly update chart repositories
Monitor release history for rollback capabilities
Validate charts before installation using linting tools

Next Steps#

Kubernetes Service for core orchestration
Configuration Guides for detailed setup
Deployment Best Practices for production deployments

Grafana Service

Mon, 01 Jan 0001 00:00:00 +0000

Grafana Service#

The Grafana service provides comprehensive visualization, monitoring dashboards, and alerting capabilities with 36 tools for creating and managing Grafana resources.

Overview#

The Grafana service in Cloud Native MCP Server enables AI assistants to manage Grafana dashboards, data sources, alerts, and other monitoring resources efficiently. It provides tools for dashboard creation, visualization management, and alert configuration.

Key Capabilities#

### 📊 Dashboard Management Complete control over Grafana dashboards including creation, updates, and sharing.

### 🗂️ Data Source Management Manage Grafana data sources with tools for configuration and testing.

### ⚠️ Alert Management Handle Grafana alerts and alert rules with configuration and monitoring tools.

### 📈 Visualization Create and manage Grafana visualizations and panels effectively.

Available Tools (36)#

Dashboard Management#

grafana-get-dashboards: Get all dashboards
grafana-get-dashboard: Get a specific dashboard
grafana-create-dashboard: Create a new dashboard
grafana-update-dashboard: Update an existing dashboard
grafana-delete-dashboard: Delete a dashboard
grafana-get-folders: Get all folders
grafana-create-folder: Create a new folder
grafana-update-folder: Update an existing folder
grafana-delete-folder: Delete a folder

Data Source Management#

grafana-get-datasources: Get all data sources
grafana-create-datasource: Create a new data source
grafana-update-datasource: Update an existing data source
grafana-delete-datasource: Delete a data source
grafana-test-datasource: Test a data source connection

Alert Management#

grafana-get-alerts: Get all alerts
grafana-get-alert: Get a specific alert
grafana-create-alert: Create a new alert
grafana-update-alert: Update an existing alert
grafana-delete-alert: Delete an alert
grafana-get-alert-rules: Get alert rules
grafana-get-alert-notifications: Get alert notification channels

User and Organization Management#

grafana-get-users: Get all users
grafana-create-user: Create a new user
grafana-update-user: Update an existing user
grafana-delete-user: Delete a user
grafana-get-orgs: Get all organizations
grafana-create-org: Create a new organization
grafana-update-org: Update an existing organization
grafana-delete-org: Delete an organization
grafana-get-teams: Get all teams
grafana-create-team: Create a new team
grafana-update-team: Update an existing team
grafana-delete-team: Delete a team

Plugin and Configuration Management#

grafana-get-plugins: Get all plugins
grafana-install-plugin: Install a plugin
grafana-uninstall-plugin: Uninstall a plugin
grafana-get-annotations: Get annotations
grafana-create-annotation: Create an annotation
grafana-get-snapshots: Get snapshots

Quick Examples#

Create a new dashboard#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23


{
 "method": "tools/call",
 "params": {
 "name": "grafana-create-dashboard",
 "arguments": {
 "dashboard": {
 "title": "My Application Dashboard",
 "panels": [
 {
 "id": 1,
 "title": "Requests per Second",
 "type": "graph",
 "targets": [
 {
 "expr": "rate(http_requests_total[5m])"
 }
 ]
 }
 ]
 }
 }
 }
}

Get all dashboards#

1
2
3
4
5
6
7


{
 "method": "tools/call",
 "params": {
 "name": "grafana-get-dashboards",
 "arguments": {}
 }
}

Add a data source#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12


{
 "method": "tools/call",
 "params": {
 "name": "grafana-create-datasource",
 "arguments": {
 "name": "Prometheus",
 "type": "prometheus",
 "url": "http://prometheus:9090",
 "access": "proxy"
 }
 }
}

Best Practices#

Organize dashboards in folders by application or team
Use consistent naming conventions for dashboards and panels
Configure appropriate alert thresholds and notification channels
Regularly review and update dashboards based on changing requirements
Implement proper user permissions and access controls

Next Steps#

Prometheus Service for metrics collection
Monitoring Guides for detailed setup
Alerting Best Practices for effective alerting

Prometheus Service

Mon, 01 Jan 0001 00:00:00 +0000

Prometheus Service#

The Prometheus service provides comprehensive metrics collection, querying, and monitoring capabilities with 20 tools for managing Prometheus resources.

Overview#

The Prometheus service in Cloud Native MCP Server enables AI assistants to query and manage Prometheus metrics efficiently. It provides tools for metric querying, alert management, and configuration management.

Key Capabilities#

### 📈 Metrics Querying Powerful querying capabilities for Prometheus metrics using PromQL.

### ⚠️ Alert Management Manage Prometheus alerts and alerting rules effectively.

### 🛠️ Configuration Handle Prometheus configuration and runtime information.

### 📊 Monitoring Access detailed monitoring data and statistics from Prometheus.

Available Tools (20)#

Query Execution#

prometheus-query: Execute instant query
prometheus-query-range: Execute range query
prometheus-query-exemplars: Query exemplar data

Metadata Queries#

prometheus-label-names: Get label names
prometheus-label-values: Get label values
prometheus-series: Get time series
prometheus-metadata: Get metadata

Target Management#

prometheus-get-targets: Get target list
prometheus-get-target-metadata: Get target metadata

Rules and Alerts Management#

prometheus-get-rules: Get rules list
prometheus-get-alerts: Get alerts list
prometheus-get-alert-managers: Get Alertmanager instances

Configuration Management#

prometheus-get-config: Get configuration information
prometheus-get-flags: Get startup flags

Status Queries#

prometheus-get-status: Get status information
prometheus-get-build-info: Get build information
prometheus-get-runtime-info: Get runtime information

TSDB Operations#

prometheus-get-tsdb-status: Get TSDB status
prometheus-get-tsdb-heatmap: Get TSDB heatmap

Quick Examples#

Query metrics for the last 5 minutes#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12


{
 "method": "tools/call",
 "params": {
 "name": "prometheus-query-range",
 "arguments": {
 "query": "up",
 "start": "5 minutes ago",
 "end": "now",
 "step": "30s"
 }
 }
}

Get all targets#

1
2
3
4
5
6
7


{
 "method": "tools/call",
 "params": {
 "name": "prometheus-get-targets",
 "arguments": {}
 }
}

Query specific metric#

1
2
3
4
5
6
7
8
9


{
 "method": "tools/call",
 "params": {
 "name": "prometheus-query",
 "arguments": {
 "query": "rate(http_requests_total[5m])"
 }
 }
}

Best Practices#

Use appropriate query ranges to avoid performance issues
Regularly review and optimize PromQL queries
Monitor target health and availability
Configure appropriate recording rules for pre-aggregated metrics
Set up proper alerting rules with appropriate thresholds

Next Steps#

Grafana Service for visualization
Monitoring Guides for detailed setup
Performance Optimization for query optimization

Kibana Service

Mon, 01 Jan 0001 00:00:00 +0000

Kibana Service#

The Kibana service provides comprehensive log analysis, visualization, and data exploration capabilities with 52 tools for managing Kibana resources.

Overview#

The Kibana service in Cloud Native MCP Server enables AI assistants to manage Kibana dashboards, visualizations, and log data efficiently. It provides tools for log analysis, data visualization, and Elasticsearch integration.

Key Capabilities#

### 🔍 Log Analysis Powerful log analysis and search capabilities with Elasticsearch integration.

### 📊 Data Visualization Create and manage Kibana dashboards and visualizations.

### 🗂️ Object Management Handle Kibana saved objects including searches, visualizations, and dashboards.

### 🌐 Elasticsearch Integration Seamless integration with Elasticsearch for data indexing and retrieval.

Available Tools (52)#

Index Management#

kibana-get-indices: Get all indices
kibana-create-index: Create a new index
kibana-delete-index: Delete an index
kibana-get-index-patterns: Get all index patterns
kibana-create-index-pattern: Create a new index pattern
kibana-delete-index-pattern: Delete an index pattern

Visualization Management#

kibana-get-visualizations: Get all visualizations
kibana-create-visualization: Create a new visualization
kibana-update-visualization: Update a visualization
kibana-delete-visualization: Delete a visualization

Dashboard Management#

kibana-get-dashboards: Get all dashboards
kibana-create-dashboard: Create a new dashboard
kibana-update-dashboard: Update a dashboard
kibana-delete-dashboard: Delete a dashboard

Search Management#

kibana-get-searches: Get all saved searches
kibana-create-search: Create a new saved search
kibana-update-search: Update a saved search
kibana-delete-search: Delete a saved search

Object Management#

kibana-get-objects: Get all saved objects
kibana-create-object: Create a new saved object
kibana-update-object: Update a saved object
kibana-delete-object: Delete a saved object

User Management#

kibana-get-users: Get all users
kibana-create-user: Create a new user
kibana-update-user: Update a user
kibana-delete-user: Delete a user

Role Management#

kibana-get-roles: Get all roles
kibana-create-role: Create a new role
kibana-update-role: Update a role
kibana-delete-role: Delete a role

Space Management#

kibana-get-spaces: Get all spaces
kibana-create-space: Create a new space
kibana-update-space: Update a space
kibana-delete-space: Delete a space

API Key Management#

kibana-get-api-keys: Get all API keys
kibana-create-api-key: Create a new API key
kibana-delete-api-key: Delete an API key

System Information#

kibana-get-status: Get Kibana status
kibana-get-info: Get Kibana information
kibana-get-config: Get Kibana configuration
kibana-get-plugins: Get installed plugins
kibana-get-license: Get license information
kibana-get-features: Get feature flags
kibana-get-telemetry: Get telemetry settings
kibana-update-telemetry: Update telemetry settings

Import/Export#

kibana-get-saved-objects: Get saved objects by type
kibana-export-objects: Export saved objects
kibana-import-objects: Import saved objects
kibana-get-maps: Get Maps saved objects
kibana-get-cases: Get Cases saved objects

Quick Examples#

Create a new index pattern#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11


{
 "method": "tools/call",
 "params": {
 "name": "kibana-create-index-pattern",
 "arguments": {
 "id": "my-app-logs-*",
 "title": "my-app-logs-*",
 "timeFieldName": "@timestamp"
 }
 }
}

Search documents#

1
2
3
4
5
6
7
8


{
 "method": "tools/call",
 "params": {
 "name": "kibana-get-searches",
 "arguments": {}
 }
 }
}

Get Kibana status#

1
2
3
4
5
6
7


{
 "method": "tools/call",
 "params": {
 "name": "kibana-get-status",
 "arguments": {}
 }
}

Best Practices#

Use appropriate index patterns for efficient log searching
Regularly review and optimize visualizations for performance
Implement proper access controls using roles and spaces
Monitor cluster health and resource usage
Use saved searches for frequently accessed data patterns

Next Steps#

Elasticsearch Service for indexing
Log Analysis Guides for detailed setup
Visualization Best Practices for effective dashboards

Elasticsearch Service

Mon, 01 Jan 0001 00:00:00 +0000

Elasticsearch Service#

The Elasticsearch service provides comprehensive log storage, search, and data indexing capabilities with 14 tools for managing Elasticsearch resources.

Overview#

The Elasticsearch service in Cloud Native MCP Server enables AI assistants to manage Elasticsearch indices, documents, and clusters efficiently. It provides tools for indexing, searching, and cluster management.

Key Capabilities#

### 🔍 Advanced Search Powerful full-text search and analytics capabilities.

### 🗂️ Index Management Complete control over Elasticsearch indices and mappings.

### 📦 Document Management Handle document indexing, retrieval, and bulk operations.

### 🖥️ Cluster Management Monitor and manage Elasticsearch cluster health and performance.

Available Tools (14)#

Index Management#

elasticsearch-get-indices: Get all indices
elasticsearch-create-index: Create a new index
elasticsearch-delete-index: Delete an index
elasticsearch-get-index-settings: Get index settings
elasticsearch-update-index-settings: Update index settings
elasticsearch-get-mappings: Get index mappings
elasticsearch-update-mappings: Update index mappings

Document Operations#

elasticsearch-index-document: Index a document
elasticsearch-get-document: Get a document
elasticsearch-search: Search documents
elasticsearch-delete-document: Delete a document

Cluster Management#

elasticsearch-get-cluster-info: Get cluster information
elasticsearch-get-cluster-health: Get cluster health
elasticsearch-get-nodes: Get cluster nodes

Quick Examples#

Index a document#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15


{
 "method": "tools/call",
 "params": {
 "name": "elasticsearch-index-document",
 "arguments": {
 "index": "my-app-logs",
 "id": "1",
 "document": {
 "timestamp": "2023-10-01T12:00:00Z",
 "level": "info",
 "message": "Application started successfully"
 }
 }
 }
}

Search documents#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14


{
 "method": "tools/call",
 "params": {
 "name": "elasticsearch-search",
 "arguments": {
 "index": "my-app-logs",
 "query": {
 "match": {
 "level": "error"
 }
 }
 }
 }
}

Get cluster health#

1
2
3
4
5
6
7


{
 "method": "tools/call",
 "params": {
 "name": "elasticsearch-get-cluster-health",
 "arguments": {}
 }
}

Best Practices#

Use appropriate index mappings for efficient searching
Regularly optimize indices for performance
Monitor cluster health and resource usage
Implement proper index lifecycle management
Use bulk operations for efficient data ingestion

Next Steps#

Kibana Service for visualization
Log Management Guides for detailed setup
Search Optimization for query performance

Alertmanager Service

Mon, 01 Jan 0001 00:00:00 +0000

Alertmanager Service#

The Alertmanager service provides comprehensive alert rules management and notifications with 15 tools for managing alerting resources.

Overview#

The Alertmanager service in Cloud Native MCP Server enables AI assistants to manage Prometheus alerts, silences, and notification routing efficiently. It provides tools for alert management, silencing, and configuration.

Key Capabilities#

### ⚠️ Alert Management Complete control over Prometheus alerts and alert groups.

### 🔕 Silence Management Manage alert silences with precise timing and matching rules.

### 📮 Notification Routing Configure notification routes and receivers for alert delivery.

### ⚙️ Configuration Manage Alertmanager configuration and status information.

Available Tools (15)#

Alert Management#

alertmanager-get-alerts: Get all alerts
alertmanager-get-alert: Get a specific alert
alertmanager-get-alert-groups: Get alert groups
alertmanager-get-receivers: Get all receivers

Silence Management#

alertmanager-get-silences: Get all silences
alertmanager-create-silence: Create a new silence
alertmanager-delete-silence: Delete a silence
alertmanager-get-alertmanagers: Get Alertmanager instances

Configuration and Status#

alertmanager-get-config: Get Alertmanager configuration
alertmanager-get-status: Get Alertmanager status
alertmanager-get-metrics: Get Alertmanager metrics
alertmanager-get-templates: Get notification templates
alertmanager-get-starttime: Get Alertmanager start time
alertmanager-get-version: Get Alertmanager version
alertmanager-get-flags: Get Alertmanager flag values

Quick Examples#

Create a silence for high CPU alerts#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17


{
 "method": "tools/call",
 "params": {
 "name": "alertmanager-create-silence",
 "arguments": {
 "matcher": {
 "name": "alertname",
 "value": "HighCPUUsage",
 "isRegex": false
 },
 "startsAt": "2023-10-01T10:00:00Z",
 "endsAt": "2023-10-01T12:00:00Z",
 "createdBy": "admin",
 "comment": "Planned maintenance window"
 }
 }
}

Get all active alerts#

1
2
3
4
5
6
7


{
 "method": "tools/call",
 "params": {
 "name": "alertmanager-get-alerts",
 "arguments": {}
 }
}

Get Alertmanager configuration#

1
2
3
4
5
6
7


{
 "method": "tools/call",
 "params": {
 "name": "alertmanager-get-config",
 "arguments": {}
 }
}

Best Practices#

Use precise matchers for effective silencing
Regularly review active alerts and silences
Configure appropriate notification routes and grouping
Monitor Alertmanager performance and health
Implement proper escalation policies for critical alerts

Next Steps#

Prometheus Service for metrics
Alerting Guides for detailed setup
Notification Configuration for routing rules

Jaeger Service

Mon, 01 Jan 0001 00:00:00 +0000

Jaeger Service#

The Jaeger service provides comprehensive distributed tracing and performance analysis with 8 tools for managing tracing resources.

Overview#

The Jaeger service in Cloud Native MCP Server enables AI assistants to analyze distributed traces, service dependencies, and performance metrics efficiently. It provides tools for trace querying, dependency analysis, and performance monitoring.

Key Capabilities#

### 📍 Trace Analysis Query and analyze distributed traces across microservices.

### 🔗 Dependency Mapping Visualize service dependencies and call graphs.

### ⚡ Performance Monitoring Analyze performance bottlenecks and latency patterns.

### 📊 Metrics Collection Collect and analyze tracing metrics and statistics.

Available Tools (8)#

Trace Management#

jaeger-get-traces: Get traces by query
jaeger-get-trace: Get a specific trace
jaeger-search-traces: Search traces with filters

Service and Operation Analysis#

jaeger-get-services: Get all services
jaeger-get-service-operations: Get operations for a service
jaeger-get-operations: Get all operations

Dependency and Metrics#

jaeger-get-dependencies: Get service dependencies
jaeger-get-metrics: Get tracing metrics

Quick Examples#

Get traces for a specific service#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10


{
 "method": "tools/call",
 "params": {
 "name": "jaeger-get-traces",
 "arguments": {
 "service": "my-app",
 "limit": 100
 }
 }
}

Get service dependencies#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10


{
 "method": "tools/call",
 "params": {
 "name": "jaeger-get-dependencies",
 "arguments": {
 "service": "my-app",
 "start": "1 hour ago"
 }
 }
}

Get all services#

1
2
3
4
5
6
7


{
 "method": "tools/call",
 "params": {
 "name": "jaeger-get-services",
 "arguments": {}
 }
}

Best Practices#

Implement proper tracing headers propagation
Use appropriate sampling strategies for performance
Regularly analyze traces for performance bottlenecks
Monitor service dependencies for architecture changes
Set up alerts based on tracing metrics and anomalies

Next Steps#

OpenTelemetry Service for metrics and logs
Tracing Guides for detailed setup
Performance Analysis for optimization

OpenTelemetry Service

Mon, 01 Jan 0001 00:00:00 +0000

OpenTelemetry Service#

The OpenTelemetry service provides comprehensive metrics, traces, and logs collection and analysis with 9 tools for managing observability resources.

Overview#

The OpenTelemetry service in Cloud Native MCP Server enables AI assistants to collect and analyze telemetry data from applications and infrastructure efficiently. It provides tools for metrics collection, trace analysis, and log aggregation.

Key Capabilities#

### 📊 Metrics Collection Collect and analyze application and infrastructure metrics.

### 📍 Trace Analysis Distributed tracing with performance insights.

### 📝 Log Aggregation Unified log collection and analysis.

### 🛠️ Configuration Manage OpenTelemetry collector configuration and status.

Available Tools (9)#

Metrics Management#

otel-get-metrics: Get metrics from OpenTelemetry collector
otel-get-metric-data: Get metric data
otel-list-metric-streams: List metric streams
otel-get-metrics-schema: Get metrics schema

Trace Management#

otel-get-traces: Get traces from OpenTelemetry collector
otel-search-traces: Search traces
otel-get-traces-schema: Get traces schema

Log and Configuration Management#

otel-get-logs: Get logs from OpenTelemetry collector
otel-get-logs-schema: Get logs schema

System Information#

otel-get-status: Get OpenTelemetry collector status
otel-get-config: Get OpenTelemetry collector configuration
otel-get-health: Get OpenTelemetry collector health
otel-get-versions: Get OpenTelemetry component versions

Quick Examples#

Get metrics from the collector#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11


{
 "method": "tools/call",
 "params": {
 "name": "otel-get-metrics",
 "arguments": {
 "metric_name": "http_requests_total",
 "start_time": "1 hour ago",
 "end_time": "now"
 }
 }
}

Get traces for a specific service#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10


{
 "method": "tools/call",
 "params": {
 "name": "otel-get-traces",
 "arguments": {
 "service_name": "my-app",
 "limit": 50
 }
 }
}

Get collector configuration#

1
2
3
4
5
6
7


{
 "method": "tools/call",
 "params": {
 "name": "otel-get-config",
 "arguments": {}
 }
}

Best Practices#

Implement proper resource attributes for effective filtering
Use appropriate sampling strategies for traces
Configure appropriate metric collection intervals
Monitor collector health and resource usage
Set up alerts based on telemetry data patterns

Next Steps#

Jaeger Service for detailed tracing
Observability Guides for detailed setup
Metrics Best Practices for collection strategies

Utilities Service

Mon, 01 Jan 0001 00:00:00 +0000

Utilities Service#

The Utilities service provides general-purpose utility tools with 6 tools for common operations and system utilities.

Overview#

The Utilities service in Cloud Native MCP Server provides general-purpose tools for common operations, data transformation, and system utilities. It provides tools for encoding, decoding, and basic data manipulation.

Key Capabilities#

### 🔧 System Utilities Common system operations and utility functions.

### 🔄 Data Transformation Encoding, decoding, and data format conversion.

### ⚙️ Configuration Tools System configuration and metadata utilities.

### 📊 Information Tools System information and statistics utilities.

Available Tools (6)#

Encoding and Transformation#

utils-base64-encode: Base64 encode
utils-base64-decode: Base64 decode
utils-json-parse: JSON parse
utils-json-stringify: JSON stringify

System Utilities#

utils-get-time: Get current server time
utils-get-uuid: Generate UUID
utils-get-stats: Get server statistics
utils-get-versions: Get component versions
utils-get-uptime: Get server uptime
utils-get-config: Get server configuration
utils-get-env: Get environment variables

Quick Examples#

Base64 encode a string#

1
2
3
4
5
6
7
8
9


{
 "method": "tools/call",
 "params": {
 "name": "utils-base64-encode",
 "arguments": {
 "input": "Hello, World!"
 }
 }
}

Get server time#

1
2
3
4
5
6
7


{
 "method": "tools/call",
 "params": {
 "name": "utils-get-time",
 "arguments": {}
 }
}

Get server statistics#

1
2
3
4
5
6
7


{
 "method": "tools/call",
 "params": {
 "name": "utils-get-stats",
 "arguments": {}
 }
}

Best Practices#

Use utility tools for common data transformations
Monitor system statistics for performance insights
Regularly check server configuration and versions
Use UUID generation for unique identifiers
Implement proper error handling for utility operations

Next Steps#

Getting Started for quick setup
Configuration Guides for detailed setup
Tools Reference for complete documentation

Showcase

Mon, 01 Jan 0001 00:00:00 +0000

Real-World Use Cases & Testimonials#

Discover how organizations are leveraging Cloud Native MCP Server to enhance their cloud-native infrastructure management and AI-assisted operations.

Use Cases#

### 🏢 Enterprise Infrastructure Management Large enterprises use Cloud Native MCP Server to manage complex Kubernetes multi-cluster environments across multiple regions. The unified interface allows DevOps teams to manage 1000+ microservices efficiently.

### 🌐 Multi-Cloud Orchestration Organizations with hybrid and multi-cloud setups leverage the unified toolset to manage resources across AWS, GCP, Azure, and on-premise environments from a single interface.

### 🤖 AI-Powered Operations Teams integrate Cloud Native MCP Server with LLMs to enable natural language infrastructure management, allowing engineers to perform complex operations with simple commands.

### 🔍 Observability Unification Companies use the integrated monitoring tools to create unified dashboards and alerts across Prometheus, Grafana, Kibana, and other observability platforms.

Customer Testimonials#

### TechCorp International "We've reduced our infrastructure management overhead by 60% since adopting Cloud Native MCP Server. The AI-assisted operations have transformed how our teams interact with Kubernetes."

### Global Finance Ltd. "The unified toolset across all our monitoring solutions has simplified our operations significantly. We can now troubleshoot issues across our entire stack in minutes instead of hours."

### CloudFirst Startup "As a fast-growing startup, we needed a solution that could scale with us. Cloud Native MCP Server provides the extensibility and performance we need while keeping operational complexity low."

### Government Services "Security and compliance are paramount for us. The audit logging and comprehensive authentication options in Cloud Native MCP Server meet our strict requirements while enabling efficient operations."

Implementation Examples#

Case Study: E-commerce Platform#

A major e-commerce platform implemented Cloud Native MCP Server to manage their Black Friday traffic operations:

Architecture Guide

Mon, 01 Jan 0001 00:00:00 +0000

Architecture Guide#

This document describes the system architecture and design principles of Cloud Native MCP Server.

Overview#

Cloud Native MCP Server is a high-performance Model Context Protocol (MCP) server for managing Kubernetes and cloud-native infrastructure. It adopts a modular design with support for multiple runtime modes and protocols.

Architecture Goals#

High Performance: Optimized caching, connection pooling, and resource management
Scalability: Modular design, easy to add new services
Security: Multi-layer authentication, input sanitization, and audit logging
Observability: Built-in metrics, logging, and tracing
Reliability: Health checks, retry mechanisms, and graceful degradation

System Architecture#

┌─────────────────────────────────────────────────────────────┐
│ Client │
│ (Claude Desktop, Browser, Custom MCP Clients) │
└────────────────────┬────────────────────────────────────────┘
 │
 │ MCP Protocol (SSE/Streamable-HTTP)
 │
┌────────────────────▼────────────────────────────────────────┐
│ HTTP Server │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ Routing Layer (SSE/Streamable-HTTP) │ │
│ └────────────────────────────────────────────────────────┘ │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ Middleware Layer │ │
│ │ - Authentication (API Key/Bearer/Basic) │ │
│ │ - Audit Logging │ │
│ │ - Rate Limiting │ │
│ │ - Security Middleware │ │
│ │ - Metrics Collection │ │
│ └────────────────────────────────────────────────────────┘ │
└────────────────────┬────────────────────────────────────────┘
 │
 │
┌────────────────────▼────────────────────────────────────────┐
│ Service Management Layer │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │Kubernetes│ │ Helm │ │ Grafana │ │Prometheus│ │
│ └──────────┘ └──────────┘ └──────────┘ └──────────┘ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ Kibana │ │Elastic │ │ AlertMgr │ │ Jaeger │ │
│ └──────────┘ └──────────┘ └──────────┘ └──────────┘ │
│ ┌──────────┐ ┌──────────┐ │
│ │ Otel │ │Utilities │ │
│ └──────────┘ └──────────┘ │
└────────────────────┬────────────────────────────────────────┘
 │
 │
┌────────────────────▼────────────────────────────────────────┐
│ Infrastructure Layer │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ Cache Layer (LRU/Segmented) │ │
│ └────────────────────────────────────────────────────────┘ │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ Secret Management │ │
│ └────────────────────────────────────────────────────────┘ │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ Logging System │ │
│ └────────────────────────────────────────────────────────┘ │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ Metrics System │ │
│ └────────────────────────────────────────────────────────┘ │
└────────────────────┬────────────────────────────────────────┘
 │
 │
┌────────────────────▼────────────────────────────────────────┐
│ External Services │
│ Kubernetes Cluster, Grafana, Prometheus, ES, etc. │
└─────────────────────────────────────────────────────────────┘

Core Components#

1. HTTP Server#

Responsibility: Handle incoming HTTP/SSE requests and connections

FAQ

Mon, 01 Jan 0001 00:00:00 +0000

Getting Started FAQ#

Which mode should I choose first?#

Use this default decision path:

streamable-http: best fit for modern MCP transport in production
sse: broad compatibility with existing MCP clients and integrations

If you are unsure, start with sse, complete validation, then migrate to streamable-http.

Why do I get `401 unauthorized`?#

Check the following in order:

MCP_AUTH_ENABLED=true is actually set in runtime environment.
MCP_AUTH_MODE is one of apikey, bearer, basic.
For apikey mode, MCP_AUTH_API_KEY is non-empty and matches request value.
API key is sent via X-Api-Key header or api_key query parameter.
Container/process was restarted after configuration changes.

Is API key header or query parameter preferred?#

Both are supported, but use request headers in production whenever possible:

Configuration Guide

Mon, 01 Jan 0001 00:00:00 +0000

Configuration Guide#

This guide covers all configuration options for Cloud Native MCP Server.

Table of Contents#

Configuration Methods
Server Configuration
Service Configuration
Authentication Configuration
Logging Configuration
Audit Logs
Cache Configuration
Performance Tuning
Example Configurations

Configuration Methods#

K8s MCP Server supports three configuration methods (in order of priority):

Command Line Arguments - Highest priority
Environment Variables - Medium priority
YAML Configuration File - Lowest priority

Configuration Priority Example#

1
2
3
4
5
6
7


# Configuration file sets default values
# Environment variables override configuration file
# Command line arguments override all settings

./cloud-native-mcp-server \
 --config=config.yaml \
 --log-level=debug

Server Configuration#

Basic Settings#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20


server:
 # Run mode: sse | streamable-http
 # Recommended: streamable-http for production, sse for broad compatibility
 mode: "sse"

 # Server listen address
 addr: "0.0.0.0:8080"

 # HTTP read timeout (seconds)
 # 0 = no timeout (not recommended for production)
 # Recommended: 30-60 seconds
 readTimeoutSec: 30

 # HTTP write timeout (seconds)
 # Should be set to 0 for SSE connections to keep them alive
 writeTimeoutSec: 0

 # HTTP idle timeout (seconds)
 # Default: 60 seconds
 idleTimeoutSec: 60

SSE Path Configuration#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31


server:
 ssePaths:
 # Kubernetes SSE endpoint
 kubernetes: "/api/kubernetes/sse"

 # Grafana SSE endpoint
 grafana: "/api/grafana/sse"

 # Prometheus SSE endpoint
 prometheus: "/api/prometheus/sse"

 # Kibana SSE endpoint
 kibana: "/api/kibana/sse"

 # Helm SSE endpoint
 helm: "/api/helm/sse"

 # Alertmanager SSE endpoint
 alertmanager: "/api/alertmanager/sse"

 # Elasticsearch SSE endpoint
 elasticsearch: "/api/elasticsearch/sse"

 # OpenTelemetry SSE endpoint
 opentelemetry: "/api/opentelemetry/sse"

 # Utilities SSE endpoint
 utilities: "/api/utilities/sse"

 # Aggregated SSE endpoint for all services
 aggregate: "/api/aggregate/sse"

Streamable-HTTP Path Configuration#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31


server:
 streamableHttpPaths:
 # Kubernetes Streamable-HTTP endpoint
 kubernetes: "/api/kubernetes/streamable-http"

 # Grafana Streamable-HTTP endpoint
 grafana: "/api/grafana/streamable-http"

 # Prometheus Streamable-HTTP endpoint
 prometheus: "/api/prometheus/streamable-http"

 # Kibana Streamable-HTTP endpoint
 kibana: "/api/kibana/streamable-http"

 # Helm Streamable-HTTP endpoint
 helm: "/api/helm/streamable-http"

 # Alertmanager Streamable-HTTP endpoint
 alertmanager: "/api/alertmanager/streamable-http"

 # Elasticsearch Streamable-HTTP endpoint
 elasticsearch: "/api/elasticsearch/streamable-http"

 # OpenTelemetry Streamable-HTTP endpoint
 opentelemetry: "/api/opentelemetry/streamable-http"

 # Utilities Streamable-HTTP endpoint
 utilities: "/api/utilities/streamable-http"

 # Aggregated Streamable-HTTP endpoint for all services
 aggregate: "/api/aggregate/streamable-http"

Command Line Arguments#

Parameter	Description	Default
`--mode`	Server mode (sse, streamable-http)	sse
`--addr`	Listen address	0.0.0.0:8080
`--config`	Configuration file path	config.yaml
`--log-level`	Log level (debug, info, warn, error)	info

Environment Variables#

Variable	Description	Default
`MCP_MODE`	Server mode	sse
`MCP_ADDR`	Listen address	0.0.0.0:8080
`MCP_LOG_LEVEL`	Log level	info

Service Configuration#

Kubernetes#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13


kubernetes:
 # kubeconfig file path
 # If empty, uses default: $KUBECONFIG → ~/.kube/config → service account
 kubeconfig: ""

 # Timeout for a single API call (seconds)
 timeoutSec: 30

 # API client queries per second (QPS)
 qps: 100.0

 # API client burst rate
 burst: 200

Prometheus#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32


prometheus:
 # Enable/disable Prometheus service
 enabled: false

 # Prometheus server address
 # Format: http://host:port or https://host:port
 address: "http://localhost:9090"

 # Request timeout (seconds)
 timeoutSec: 30

 # Basic auth username (optional)
 username: ""

 # Basic auth password (optional)
 password: ""

 # Bearer token authentication (optional, higher priority than Basic Auth)
 bearerToken: ""

 # Skip TLS certificate verification
 # Do not use in production!
 tlsSkipVerify: false

 # TLS client certificate file path (for mTLS authentication)
 tlsCertFile: ""

 # TLS client key file path
 tlsKeyFile: ""

 # TLS CA certificate file path
 tlsCAFile: ""

Grafana#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20


grafana:
 # Enable/disable Grafana service
 enabled: false

 # Grafana server URL
 # Format: http://host:port or https://host:port
 url: "http://localhost:3000"

 # Grafana API Key (recommended)
 # Create in Grafana: Administration → API Keys
 apiKey: ""

 # Basic auth username (alternative to API Key)
 username: ""

 # Basic auth password
 password: ""

 # Request timeout (seconds)
 timeoutSec: 30

Kibana#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28


kibana:
 # Enable/disable Kibana service
 enabled: false

 # Kibana server URL
 # Format: http://host:port or https://host:port
 url: "https://localhost:5601"

 # Kibana API Key (recommended)
 # Create in Kibana: Stack Management → API Keys
 apiKey: ""

 # Basic auth username (alternative to API Key)
 username: ""

 # Basic auth password
 password: ""

 # Request timeout (seconds)
 timeoutSec: 30

 # Skip TLS certificate verification
 # Do not use in production!
 skipVerify: false

 # Kibana space name
 # Default: "default"
 space: "default"

Helm#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33


helm:
 # Enable/disable Helm service
 enabled: false

 # Helm operations kubeconfig path
 # If empty, uses the same kubeconfig as Kubernetes client
 kubeconfigPath: ""

 # Default namespace for Helm operations
 namespace: "default"

 # Enable Helm debug mode
 debug: false

 # Repository update timeout (seconds)
 # Default: 300 (5 minutes)
 # Recommended for China: 600-900
 timeoutSec: 300

 # Maximum retry attempts
 # Number of retries for failed repository updates
 # Default: 3
 # Recommended: 3-5
 maxRetries: 3

 # Enable mirrors
 # Used to accelerate Helm repository pulls
 # Default: false
 useMirrors: false

 # Custom mirror mapping
 # Format: original repository URL -> mirror URL
 mirrors: {}

Elasticsearch#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40


elasticsearch:
 # Enable/disable Elasticsearch service
 enabled: false

 # Elasticsearch server addresses (supports multi-node HA)
 addresses:
 - "http://localhost:9200"

 # Single Elasticsearch server address (alternative to addresses)
 # Used when addresses is empty
 address: ""

 # Basic auth username
 username: ""

 # Basic auth password
 password: ""

 # Bearer token authentication (optional, higher priority than Basic Auth)
 bearerToken: ""

 # API Key authentication (optional, highest priority)
 # Format: id:api_key
 apiKey: ""

 # Request timeout (seconds)
 timeoutSec: 30

 # Skip TLS certificate verification
 # Do not use in production!
 tlsSkipVerify: false

 # TLS client certificate file path (for mTLS authentication)
 tlsCertFile: ""

 # TLS client key file path
 tlsKeyFile: ""

 # TLS CA certificate file path
 tlsCAFile: ""

Alertmanager#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32


alertmanager:
 # Enable/disable Alertmanager service
 enabled: false

 # Alertmanager server address
 # Format: http://host:port or https://host:port
 address: "http://localhost:9093"

 # Request timeout (seconds)
 timeoutSec: 30

 # Basic auth username (optional)
 username: ""

 # Basic auth password (optional)
 password: ""

 # Bearer token authentication (optional, higher priority than Basic Auth)
 bearerToken: ""

 # Skip TLS certificate verification
 # Do not use in production!
 tlsSkipVerify: false

 # TLS client certificate file path (for mTLS authentication)
 tlsCertFile: ""

 # TLS client key file path
 tlsKeyFile: ""

 # TLS CA certificate file path
 tlsCAFile: ""

OpenTelemetry#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32


opentelemetry:
 # Enable/disable OpenTelemetry service
 enabled: false

 # OpenTelemetry Collector address
 # Format: http://host:port or https://host:port
 address: "http://localhost:4318"

 # Request timeout (seconds)
 timeoutSec: 30

 # Basic auth username (optional)
 username: ""

 # Basic auth password (optional)
 password: ""

 # Bearer token authentication (optional, higher priority than Basic Auth)
 bearerToken: ""

 # Skip TLS certificate verification
 # Do not use in production!
 tlsSkipVerify: false

 # TLS client certificate file path (for mTLS authentication)
 tlsCertFile: ""

 # TLS client key file path
 tlsKeyFile: ""

 # TLS CA certificate file path
 tlsCAFile: ""

Utilities#

1
2
3


utilities:
 # Utilities service is always enabled
 enabled: true

Authentication Configuration#

API Key Authentication#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29


auth:
 # Enable/disable authentication
 enabled: false

 # Authentication mode: apikey | bearer | basic
 # apikey: X-API-Key simple API key authentication
 # bearer: Bearer Token (JWT) authentication
 # basic: HTTP Basic Auth
 mode: "apikey"

 # API Key (for apikey mode)
 # Minimum 8 characters, recommended 16+ characters
 apiKey: ""

 # Bearer token (for bearer mode)
 # Minimum 16 characters recommended (JWT token)
 bearerToken: ""

 # Basic Auth username
 username: ""

 # Basic Auth password
 password: ""

 # JWT secret (for JWT verification)
 jwtSecret: ""

 # JWT algorithm (HS256, RS256, etc.)
 jwtAlgorithm: "HS256"

Authentication Environment Variables#

Variable	Description
`MCP_AUTH_ENABLED`	Enable authentication (1, true, yes, on)
`MCP_AUTH_MODE`	Authentication mode (apikey, bearer, basic)
`MCP_AUTH_API_KEY`	API key or bearer token
`MCP_AUTH_USERNAME`	Basic auth username
`MCP_AUTH_PASSWORD`	Basic auth password
`MCP_AUTH_JWT_SECRET`	JWT secret
`MCP_AUTH_JWT_ALGORITHM`	JWT algorithm

Logging Configuration#

1
2
3
4
5
6
7


logging:
 # Log level: debug | info | warn | error
 level: "info"

 # Use JSON format logs
 # Suitable for log aggregation systems (ELK, Splunk, etc.)
 json: false

Log Level Description#

debug: Detailed debugging information, including all requests and responses
info: General information, including important operations and status changes
warn: Warning information, does not affect functionality but needs attention
error: Error information, functionality is impaired

Audit Logs#

Basic Configuration#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20


audit:
 # Enable/disable audit logging
 enabled: false

 # Audit log level: debug | info | warn | error
 level: "info"

 # Audit log storage: stdout | file | database | all
 storage: "memory"

 # Log format: text | json
 # json: Structured JSON format, suitable for log aggregation
 # text: Human-readable text format
 format: "json"

 # Maximum query results
 maxResults: 1000

 # Query time range (days)
 timeRange: 90

File Storage Configuration#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20


audit:
 storage: "file"
 file:
 # Log file path
 path: "/var/log/cloud-native-mcp-server/audit.log"

 # Maximum log file size (MB)
 maxSizeMB: 100

 # Maximum number of backup files
 maxBackups: 10

 # Maximum log file age (days)
 maxAgeDays: 30

 # Compress rotated log files
 compress: true

 # Maximum number of logs in memory storage
 maxLogs: 10000

Database Storage Configuration#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23


audit:
 storage: "database"
 database:
 # Database type: sqlite | postgresql | mysql
 type: "sqlite"

 # SQLite database file path
 # Used only when type="sqlite"
 sqlitePath: "/var/lib/cloud-native-mcp-server/audit.db"

 # PostgreSQL connection string
 # Used only when type="postgresql"
 # Format: postgresql://user:password@host:port/dbname
 connectionString: ""

 # Database table name
 tableName: "audit_logs"

 # Maximum number of records
 maxRecords: 100000

 # Cleanup interval (hours)
 cleanupInterval: 24

Query API Configuration#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10


audit:
 query:
 # Enable query API
 enabled: true

 # Maximum results per query
 maxResults: 1000

 # Maximum time range (days)
 timeRange: 90

Sensitive Data Masking Configuration#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17


audit:
 masking:
 # Enable masking
 enabled: true

 # Fields to mask
 fields:
 - password
 - token
 - apiKey
 - secret
 - passwd
 - pwd
 - authorization

 # Mask replacement value
 maskValue: "***REDACTED***"

Sampling Configuration (High Traffic Scenarios)#

1
2
3
4
5
6
7
8


audit:
 sampling:
 # Enable sampling
 enabled: false

 # Sampling rate (0-1)
 # 1.0 = log all, 0.1 = log 10%
 rate: 1.0

Service and Tool Filtering#

1
2
3
4
5
6
7
8
9


enableDisable:
 # Disabled services (comma-separated)
 disabledServices: []

 # Enabled services (comma-separated, overrides disabled list)
 enabledServices: []

 # Disabled tools (comma-separated)
 disabledTools: []

Performance Tuning#

Use currently supported tuning knobs:

Troubleshooting

Mon, 01 Jan 0001 00:00:00 +0000

Troubleshooting#

Use this page as a practical playbook when setup or runtime behavior is not as expected.

1. Server fails to start#

Check port conflicts and startup logs:

1
2
3
4
5


# Check if port is occupied
ss -lntp | rg 8080

# Start with debug logs
./cloud-native-mcp-server --mode=sse --addr=127.0.0.1:8080 --log-level=debug

If using Docker, inspect container logs:

Deployment Guide

Mon, 01 Jan 0001 00:00:00 +0000

Deployment Guide#

This guide covers various deployment strategies and best practices for Cloud Native MCP Server.

Table of Contents#

Prerequisites
Quick Deployment
Kubernetes Deployment
Docker Deployment
Helm Deployment
Production Considerations
Monitoring and Observability
Security Best Practices
Troubleshooting

Prerequisites#

System Requirements#

Operating System: Linux, macOS, or Windows
CPU: Minimum 1 core, recommended 2+ cores
Memory: Minimum 512MB, recommended 1GB+
Disk: Minimum 100MB
Network: Access to Kubernetes cluster and configured services

Software Requirements#

Go: 1.25+ (building from source)
Docker: 20.10+ (containerized deployment)
kubectl: Configured cluster access
Helm: 3.0+ (Helm deployment)

Service Dependencies#

Optional services to connect to:

Security Guide

Mon, 01 Jan 0001 00:00:00 +0000

Security Guide#

This document describes the security features and best practices for Cloud Native MCP Server.

Table of Contents#

Authentication
Secret Management
Input Sanitization
Audit Logging
Security Best Practices
Security Headers
Reporting Security Issues

Authentication#

API Key Authentication#

API keys must meet the following complexity requirements:

Minimum Length: 16 characters
Character Types: Must include at least 3 of the following 4 types:
- Uppercase letters (A-Z)
- Lowercase letters (a-z)
- Numbers (0-9)
- Special characters (!@#$%^&*()_+-=[]{}|;:,.<>?)

Valid Examples:

Performance Guide

Mon, 01 Jan 0001 00:00:00 +0000

Performance Guide#

This guide focuses on performance tuning that matches the current Cloud Native MCP Server implementation.

What You Can Tune Today#

1. Server Timeouts#

1
2
3
4


server:
 readTimeoutSec: 30
 writeTimeoutSec: 0
 idleTimeoutSec: 60

Recommendations:

Keep writeTimeoutSec: 0 for SSE-heavy workloads.
Increase readTimeoutSec for slow clients or large request bodies.
Increase idleTimeoutSec for long-lived clients behind proxies.

2. Kubernetes Client Throughput#

1
2
3
4


kubernetes:
 timeoutSec: 30
 qps: 100.0
 burst: 200

Recommendations:

Tools Reference

Mon, 01 Jan 0001 00:00:00 +0000

Tools Reference#

Cloud Native MCP Server provides 220+ powerful tools covering Kubernetes management, application deployment, monitoring, log analysis, and more.

### 🚀 Kubernetes (28 tools) Core container orchestration and resource management

### 📦 Helm (31 tools) Application package management and deployment

### 📊 Grafana (36 tools) Visualization, monitoring dashboards, and alerting

### 📈 Prometheus (20 tools) Metrics collection, querying, and monitoring

### 🔍 Kibana (52 tools) Log analysis, visualization, and data exploration

### ⚡ Elasticsearch (14 tools) Log storage, search, and data indexing

### ⚠️ Alertmanager (15 tools) Alert rules management and notifications

### 📍 Jaeger (8 tools) Distributed tracing and performance analysis

### 🌐 OpenTelemetry (9 tools) Metrics, traces, and logs collection and analysis

### 🔧 Utilities (6 tools) General-purpose utility tools

Kubernetes Tools (28)#

The Kubernetes service provides comprehensive cluster management capabilities:

API Documentation

Mon, 01 Jan 0001 00:00:00 +0000

API Documentation#

This page documents the runtime endpoints exposed by Cloud Native MCP Server.

Base Address#

1

http://localhost:8080

Transport Modes and Endpoints#

Cloud Native MCP Server supports two runtime modes:

Mode	Typical Usage	Aggregate Endpoint
`sse`	Broad MCP client compatibility	`/api/aggregate/sse`
`streamable-http`	Modern MCP transport	`/api/aggregate/streamable-http`

Service-specific endpoint pattern:

SSE: /api/<service>/sse
Streamable HTTP: /api/<service>/streamable-http

Common service names include kubernetes, helm, grafana, prometheus, kibana, elasticsearch, alertmanager, jaeger, opentelemetry, utilities, and aggregate.

Sitemap

Mon, 01 Jan 0001 00:00:00 +0000

Sitemap#

This page provides a comprehensive overview of all pages available on the Cloud Native MCP Server website.

Main Pages#

Services#

Documentation#

Guides#

Configuration Guides#

Deployment Guides#

Security Guides#

Performance Guides#

Concepts#

Tools#

AI Integration Best Practices: Getting the Most from MCP

Sat, 01 Feb 2025 10:00:00 +0000

Cloud Native MCP Server is designed for AI-assisted infrastructure operations. This guide focuses on practical integration patterns that are safe and production-friendly.

Understand the Interaction Model#

The Model Context Protocol (MCP) enables AI clients to discover tools and call them through a standard workflow.

Tool Discovery#

1
2
3
4


{
 "method": "mcp/list-tools",
 "params": {}
}

Use discovery first so your agent can reason with the latest available tools and parameter schemas.

Performance Optimization Tips for Cloud Native MCP Server

Wed, 15 Jan 2025 10:00:00 +0000

Learn how to optimize Cloud Native MCP Server for predictable latency and higher throughput in real production workloads.

Cache and Response Strategy#

The server already includes internal cache and response shaping mechanisms. You can improve performance further by reducing response scope per call:

Prefer namespace-scoped queries over cluster-wide queries.
Use pagination parameters (for tools that support them) on large datasets.
Query only the fields you actually need for the current decision.

Example: Limit payload size#

1
2
3
4
5
6
7


{
 "method": "kubernetes-get-pods",
 "params": {
 "namespace": "default",
 "limit": 50
 }
}

Tune Kubernetes and Service Timeouts#

Use runtime variables that are supported by the current server:

Introducing Cloud Native MCP Server: The Ultimate Infrastructure Management Solution

Wed, 01 Jan 2025 10:00:00 +0000

Cloud Native MCP Server represents a breakthrough in cloud-native infrastructure management, combining the power of 10 essential services with 220+ tools into a single, unified interface that enables AI-assisted operations like never before.

The Challenge of Modern Infrastructure#

Today’s cloud-native environments are incredibly complex. Organizations manage applications across multiple Kubernetes clusters, utilize dozens of monitoring tools, and struggle with fragmented toolsets that don’t speak the same language. Engineers spend more time context-switching between tools than actually optimizing their infrastructure.

Architecture Guide

Mon, 01 Jan 0001 00:00:00 +0000

Architecture Guide#

This document describes the system architecture and design principles of Cloud Native MCP Server.

Table of Contents#

Overview
System Architecture
Core Components
Service Integration
Data Flow
Design Principles
Performance Optimization
Scalability

Overview#

Architecture Goals#

High Performance: Optimized caching, connection pooling, and resource management
Scalability: Modular design, easy to add new services
Security: Multi-layer authentication, input sanitization, and audit logging
Observability: Built-in metrics, logging, and tracing
Reliability: Health checks, retry mechanisms, and graceful degradation

System Architecture#

┌─────────────────────────────────────────────────────────────┐
│ Client │
│ (Claude Desktop, Browser, Custom MCP Clients) │
└────────────────────┬────────────────────────────────────────┘
 │
 │ MCP Protocol (SSE/Streamable-HTTP)
 │
┌────────────────────▼────────────────────────────────────────┐
│ HTTP Server │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ Routing Layer (SSE/Streamable-HTTP) │ │
│ └────────────────────────────────────────────────────────┘ │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ Middleware Layer │ │
│ │ - Authentication (API Key/Bearer/Basic) │ │
│ │ - Audit Logging │ │
│ │ - Rate Limiting │ │
│ │ - Security Middleware │ │
│ │ - Metrics Collection │ │
│ └────────────────────────────────────────────────────────┘ │
└────────────────────┬────────────────────────────────────────┘
 │
 │
┌────────────────────▼────────────────────────────────────────┐
│ Service Management Layer │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │Kubernetes│ │ Helm │ │ Grafana │ │Prometheus│ │
│ └──────────┘ └──────────┘ └──────────┘ └──────────┘ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ Kibana │ │Elastic │ │ AlertMgr │ │ Jaeger │ │
│ └──────────┘ └──────────┘ └──────────┘ └──────────┘ │
│ ┌──────────┐ ┌──────────┐ │
│ │ Otel │ │Utilities │ │
│ └──────────┘ └──────────┘ │
└────────────────────┬────────────────────────────────────────┘
 │
 │
┌────────────────────▼────────────────────────────────────────┐
│ Infrastructure Layer │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ Cache Layer (LRU/Segmented) │ │
│ └────────────────────────────────────────────────────────┘ │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ Secret Management │ │
│ └────────────────────────────────────────────────────────┘ │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ Logging System │ │
│ └────────────────────────────────────────────────────────┘ │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ Metrics System │ │
│ └────────────────────────────────────────────────────────┘ │
└────────────────────┬────────────────────────────────────────┘
 │
 │
┌────────────────────▼────────────────────────────────────────┐
│ External Services │
│ Kubernetes Cluster, Grafana, Prometheus, ES, etc. │
└─────────────────────────────────────────────────────────────┘

Core Components#

1. HTTP Server#

Responsibility: Handle incoming HTTP/SSE requests and connections

Configuration Guide

Mon, 01 Jan 0001 00:00:00 +0000

Configuration Guide#

This guide covers all configuration options for Cloud Native MCP Server.

Table of Contents#

Configuration Methods
Server Configuration
Service Configuration
Authentication Configuration
Logging Configuration
Audit Logs
Cache Configuration
Performance Tuning
Example Configurations

Configuration Methods#

K8s MCP Server supports three configuration methods (in order of priority):

Command Line Arguments - Highest priority
Environment Variables - Medium priority
YAML Configuration File - Lowest priority

Configuration Priority Example#

1
2
3
4
5
6
7


# Configuration file sets default values
# Environment variables override configuration file
# Command line arguments override all settings

./cloud-native-mcp-server \
 --config=config.yaml \
 --log-level=debug

Server Configuration#

Basic Settings#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20


server:
 # Run mode: sse | streamable-http
 # Recommended: streamable-http for production, sse for broad compatibility
 mode: "sse"

 # Server listen address
 addr: "0.0.0.0:8080"

 # HTTP read timeout (seconds)
 # 0 = no timeout (not recommended for production)
 # Recommended: 30-60 seconds
 readTimeoutSec: 30

 # HTTP write timeout (seconds)
 # Should be set to 0 for SSE connections to keep them alive
 writeTimeoutSec: 0

 # HTTP idle timeout (seconds)
 # Default: 60 seconds
 idleTimeoutSec: 60

SSE Path Configuration#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31


server:
 ssePaths:
 # Kubernetes SSE endpoint
 kubernetes: "/api/kubernetes/sse"

 # Grafana SSE endpoint
 grafana: "/api/grafana/sse"

 # Prometheus SSE endpoint
 prometheus: "/api/prometheus/sse"

 # Kibana SSE endpoint
 kibana: "/api/kibana/sse"

 # Helm SSE endpoint
 helm: "/api/helm/sse"

 # Alertmanager SSE endpoint
 alertmanager: "/api/alertmanager/sse"

 # Elasticsearch SSE endpoint
 elasticsearch: "/api/elasticsearch/sse"

 # OpenTelemetry SSE endpoint
 opentelemetry: "/api/opentelemetry/sse"

 # Utilities SSE endpoint
 utilities: "/api/utilities/sse"

 # Aggregated SSE endpoint for all services
 aggregate: "/api/aggregate/sse"

Streamable-HTTP Path Configuration#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31


server:
 streamableHttpPaths:
 # Kubernetes Streamable-HTTP endpoint
 kubernetes: "/api/kubernetes/streamable-http"

 # Grafana Streamable-HTTP endpoint
 grafana: "/api/grafana/streamable-http"

 # Prometheus Streamable-HTTP endpoint
 prometheus: "/api/prometheus/streamable-http"

 # Kibana Streamable-HTTP endpoint
 kibana: "/api/kibana/streamable-http"

 # Helm Streamable-HTTP endpoint
 helm: "/api/helm/streamable-http"

 # Alertmanager Streamable-HTTP endpoint
 alertmanager: "/api/alertmanager/streamable-http"

 # Elasticsearch Streamable-HTTP endpoint
 elasticsearch: "/api/elasticsearch/streamable-http"

 # OpenTelemetry Streamable-HTTP endpoint
 opentelemetry: "/api/opentelemetry/streamable-http"

 # Utilities Streamable-HTTP endpoint
 utilities: "/api/utilities/streamable-http"

 # Aggregated Streamable-HTTP endpoint for all services
 aggregate: "/api/aggregate/streamable-http"

Command Line Arguments#

Parameter	Description	Default
`--mode`	Server mode (sse, streamable-http)	sse
`--addr`	Listen address	0.0.0.0:8080
`--config`	Configuration file path	config.yaml
`--log-level`	Log level (debug, info, warn, error)	info

Environment Variables#

Variable	Description	Default
`MCP_MODE`	Server mode	sse
`MCP_ADDR`	Listen address	0.0.0.0:8080
`MCP_LOG_LEVEL`	Log level	info

Service Configuration#

Kubernetes#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13


kubernetes:
 # kubeconfig file path
 # If empty, uses default: $KUBECONFIG → ~/.kube/config → service account
 kubeconfig: ""

 # Timeout for a single API call (seconds)
 timeoutSec: 30

 # API client queries per second (QPS)
 qps: 100.0

 # API client burst rate
 burst: 200

Prometheus#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32


prometheus:
 # Enable/disable Prometheus service
 enabled: false

 # Prometheus server address
 # Format: http://host:port or https://host:port
 address: "http://localhost:9090"

 # Request timeout (seconds)
 timeoutSec: 30

 # Basic auth username (optional)
 username: ""

 # Basic auth password (optional)
 password: ""

 # Bearer token authentication (optional, higher priority than Basic Auth)
 bearerToken: ""

 # Skip TLS certificate verification
 # Do not use in production!
 tlsSkipVerify: false

 # TLS client certificate file path (for mTLS authentication)
 tlsCertFile: ""

 # TLS client key file path
 tlsKeyFile: ""

 # TLS CA certificate file path
 tlsCAFile: ""

Grafana#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20


grafana:
 # Enable/disable Grafana service
 enabled: false

 # Grafana server URL
 # Format: http://host:port or https://host:port
 url: "http://localhost:3000"

 # Grafana API Key (recommended)
 # Create in Grafana: Administration → API Keys
 apiKey: ""

 # Basic auth username (alternative to API Key)
 username: ""

 # Basic auth password
 password: ""

 # Request timeout (seconds)
 timeoutSec: 30

Kibana#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28


kibana:
 # Enable/disable Kibana service
 enabled: false

 # Kibana server URL
 # Format: http://host:port or https://host:port
 url: "https://localhost:5601"

 # Kibana API Key (recommended)
 # Create in Kibana: Stack Management → API Keys
 apiKey: ""

 # Basic auth username (alternative to API Key)
 username: ""

 # Basic auth password
 password: ""

 # Request timeout (seconds)
 timeoutSec: 30

 # Skip TLS certificate verification
 # Do not use in production!
 skipVerify: false

 # Kibana space name
 # Default: "default"
 space: "default"

Helm#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33


helm:
 # Enable/disable Helm service
 enabled: false

 # Helm operations kubeconfig path
 # If empty, uses the same kubeconfig as Kubernetes client
 kubeconfigPath: ""

 # Default namespace for Helm operations
 namespace: "default"

 # Enable Helm debug mode
 debug: false

 # Repository update timeout (seconds)
 # Default: 300 (5 minutes)
 # Recommended for China: 600-900
 timeoutSec: 300

 # Maximum retry attempts
 # Number of retries for failed repository updates
 # Default: 3
 # Recommended: 3-5
 maxRetries: 3

 # Enable mirrors
 # Used to accelerate Helm repository pulls
 # Default: false
 useMirrors: false

 # Custom mirror mapping
 # Format: original repository URL -> mirror URL
 mirrors: {}

Elasticsearch#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40


elasticsearch:
 # Enable/disable Elasticsearch service
 enabled: false

 # Elasticsearch server addresses (supports multi-node HA)
 addresses:
 - "http://localhost:9200"

 # Single Elasticsearch server address (alternative to addresses)
 # Used when addresses is empty
 address: ""

 # Basic auth username
 username: ""

 # Basic auth password
 password: ""

 # Bearer token authentication (optional, higher priority than Basic Auth)
 bearerToken: ""

 # API Key authentication (optional, highest priority)
 # Format: id:api_key
 apiKey: ""

 # Request timeout (seconds)
 timeoutSec: 30

 # Skip TLS certificate verification
 # Do not use in production!
 tlsSkipVerify: false

 # TLS client certificate file path (for mTLS authentication)
 tlsCertFile: ""

 # TLS client key file path
 tlsKeyFile: ""

 # TLS CA certificate file path
 tlsCAFile: ""

Alertmanager#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32


alertmanager:
 # Enable/disable Alertmanager service
 enabled: false

 # Alertmanager server address
 # Format: http://host:port or https://host:port
 address: "http://localhost:9093"

 # Request timeout (seconds)
 timeoutSec: 30

 # Basic auth username (optional)
 username: ""

 # Basic auth password (optional)
 password: ""

 # Bearer token authentication (optional, higher priority than Basic Auth)
 bearerToken: ""

 # Skip TLS certificate verification
 # Do not use in production!
 tlsSkipVerify: false

 # TLS client certificate file path (for mTLS authentication)
 tlsCertFile: ""

 # TLS client key file path
 tlsKeyFile: ""

 # TLS CA certificate file path
 tlsCAFile: ""

OpenTelemetry#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32


opentelemetry:
 # Enable/disable OpenTelemetry service
 enabled: false

 # OpenTelemetry Collector address
 # Format: http://host:port or https://host:port
 address: "http://localhost:4318"

 # Request timeout (seconds)
 timeoutSec: 30

 # Basic auth username (optional)
 username: ""

 # Basic auth password (optional)
 password: ""

 # Bearer token authentication (optional, higher priority than Basic Auth)
 bearerToken: ""

 # Skip TLS certificate verification
 # Do not use in production!
 tlsSkipVerify: false

 # TLS client certificate file path (for mTLS authentication)
 tlsCertFile: ""

 # TLS client key file path
 tlsKeyFile: ""

 # TLS CA certificate file path
 tlsCAFile: ""

Utilities#

1
2
3


utilities:
 # Utilities service is always enabled
 enabled: true

Authentication Configuration#

API Key Authentication#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29


auth:
 # Enable/disable authentication
 enabled: false

 # Authentication mode: apikey | bearer | basic
 # apikey: X-API-Key simple API key authentication
 # bearer: Bearer Token (JWT) authentication
 # basic: HTTP Basic Auth
 mode: "apikey"

 # API Key (for apikey mode)
 # Minimum 8 characters, recommended 16+ characters
 apiKey: ""

 # Bearer token (for bearer mode)
 # Minimum 16 characters recommended (JWT token)
 bearerToken: ""

 # Basic Auth username
 username: ""

 # Basic Auth password
 password: ""

 # JWT secret (for JWT verification)
 jwtSecret: ""

 # JWT algorithm (HS256, RS256, etc.)
 jwtAlgorithm: "HS256"

Authentication Environment Variables#

Variable	Description
`MCP_AUTH_ENABLED`	Enable authentication (1, true, yes, on)
`MCP_AUTH_MODE`	Authentication mode (apikey, bearer, basic)
`MCP_AUTH_API_KEY`	API key or bearer token
`MCP_AUTH_USERNAME`	Basic auth username
`MCP_AUTH_PASSWORD`	Basic auth password
`MCP_AUTH_JWT_SECRET`	JWT secret
`MCP_AUTH_JWT_ALGORITHM`	JWT algorithm

Logging Configuration#

1
2
3
4
5
6
7


logging:
 # Log level: debug | info | warn | error
 level: "info"

 # Use JSON format logs
 # Suitable for log aggregation systems (ELK, Splunk, etc.)
 json: false

Log Level Description#

debug: Detailed debugging information, including all requests and responses
info: General information, including important operations and status changes
warn: Warning information, does not affect functionality but needs attention
error: Error information, functionality is impaired

Audit Logs#

Basic Configuration#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20


audit:
 # Enable/disable audit logging
 enabled: false

 # Audit log level: debug | info | warn | error
 level: "info"

 # Audit log storage: stdout | file | database | all
 storage: "memory"

 # Log format: text | json
 # json: Structured JSON format, suitable for log aggregation
 # text: Human-readable text format
 format: "json"

 # Maximum query results
 maxResults: 1000

 # Query time range (days)
 timeRange: 90

File Storage Configuration#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20


audit:
 storage: "file"
 file:
 # Log file path
 path: "/var/log/cloud-native-mcp-server/audit.log"

 # Maximum log file size (MB)
 maxSizeMB: 100

 # Maximum number of backup files
 maxBackups: 10

 # Maximum log file age (days)
 maxAgeDays: 30

 # Compress rotated log files
 compress: true

 # Maximum number of logs in memory storage
 maxLogs: 10000

Database Storage Configuration#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23


audit:
 storage: "database"
 database:
 # Database type: sqlite | postgresql | mysql
 type: "sqlite"

 # SQLite database file path
 # Used only when type="sqlite"
 sqlitePath: "/var/lib/cloud-native-mcp-server/audit.db"

 # PostgreSQL connection string
 # Used only when type="postgresql"
 # Format: postgresql://user:password@host:port/dbname
 connectionString: ""

 # Database table name
 tableName: "audit_logs"

 # Maximum number of records
 maxRecords: 100000

 # Cleanup interval (hours)
 cleanupInterval: 24

Query API Configuration#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10


audit:
 query:
 # Enable query API
 enabled: true

 # Maximum results per query
 maxResults: 1000

 # Maximum time range (days)
 timeRange: 90

Sensitive Data Masking Configuration#

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17


audit:
 masking:
 # Enable masking
 enabled: true

 # Fields to mask
 fields:
 - password
 - token
 - apiKey
 - secret
 - passwd
 - pwd
 - authorization

 # Mask replacement value
 maskValue: "***REDACTED***"

Sampling Configuration (High Traffic Scenarios)#

1
2
3
4
5
6
7
8


audit:
 sampling:
 # Enable sampling
 enabled: false

 # Sampling rate (0-1)
 # 1.0 = log all, 0.1 = log 10%
 rate: 1.0

Service and Tool Filtering#

1
2
3
4
5
6
7
8
9


enableDisable:
 # Disabled services (comma-separated)
 disabledServices: []

 # Enabled services (comma-separated, overrides disabled list)
 enabledServices: []

 # Disabled tools (comma-separated)
 disabledTools: []

Performance Tuning#

Use currently supported tuning knobs:

Deployment Guide

Mon, 01 Jan 0001 00:00:00 +0000

Deployment Guide#

This guide covers various deployment strategies and best practices for Cloud Native MCP Server.

Table of Contents#

Prerequisites
Quick Deployment
Kubernetes Deployment
Docker Deployment
Helm Deployment
Production Considerations
Monitoring and Observability
Security Best Practices
Troubleshooting

Prerequisites#

System Requirements#

Operating System: Linux, macOS, or Windows
CPU: Minimum 1 core, recommended 2+ cores
Memory: Minimum 512MB, recommended 1GB+
Disk: Minimum 100MB
Network: Access to Kubernetes cluster and configured services

Software Requirements#

Go: 1.25+ (building from source)
Docker: 20.10+ (containerized deployment)
kubectl: Configured cluster access
Helm: 3.0+ (Helm deployment)

Service Dependencies#

Optional services to connect to:

Performance Guide

Mon, 01 Jan 0001 00:00:00 +0000

Performance Guide#

This guide focuses on performance tuning that matches the current Cloud Native MCP Server implementation.

What You Can Tune Today#

1. Server Timeouts#

1
2
3
4


server:
 readTimeoutSec: 30
 writeTimeoutSec: 0
 idleTimeoutSec: 60

Recommendations:

Keep writeTimeoutSec: 0 for SSE-heavy workloads.
Increase readTimeoutSec for slow clients or large request bodies.
Increase idleTimeoutSec for long-lived clients behind proxies.

2. Kubernetes Client Throughput#

1
2
3
4


kubernetes:
 timeoutSec: 30
 qps: 100.0
 burst: 200

Recommendations:

Security Guide

Mon, 01 Jan 0001 00:00:00 +0000

Security Guide#

This document describes the security features and best practices for Cloud Native MCP Server.

Table of Contents#

Authentication
Secret Management
Input Sanitization
Audit Logging
Security Best Practices
Security Headers
Reporting Security Issues

Authentication#

API Key Authentication#

API keys must meet the following complexity requirements:

Minimum Length: 16 characters
Character Types: Must include at least 3 of the following 4 types:
- Uppercase letters (A-Z)
- Lowercase letters (a-z)
- Numbers (0-9)
- Special characters (!@#$%^&*()_+-=[]{}|;:,.<>?)

Valid Examples: