mcp-servers
by JPishikawa
Overview
These servers provide a 'Model Context Protocol' (MCP) interface for various external services, including Slack, Kubernetes, GitHub, and Weather APIs, primarily to serve as context providers for AI Agents.
Installation
No command providedEnvironment Variables
- SLACK_MCP_XOXP_TOKEN
- LOGS_CHANNEL_ID
- WEATHER_API_KEY
Security Notes
The 'weather-mcp.yaml' contains a hardcoded 'WEATHER_API_KEY' set to 'demo-key'. While labeled as a demo key, hardcoding API keys is a significant security risk and a poor practice, potentially leading to exposure of real keys in production. The 'kubernetes-mcp.yaml' grants broad read-only access (get, list, watch) to numerous Kubernetes resources (pods, events, services, secrets, deployments, etc.) via a ClusterRole. While intended for observability, this constitutes a wide attack surface if the server itself is compromised.
Similar Servers
klavis
Develop and deploy AI agents that interact with a wide array of web services (e.g., Gmail, YouTube, LinkedIn, Supabase, Salesforce, Kubernetes) through a standardized Model Context Protocol (MCP), often orchestrated by an intelligent routing layer like Strata.
slack-mcp-client
This client bridges Slack with AI models and external tools via the Model Context Protocol (MCP), enabling AI to interact with real systems and data through Slack conversations.
osmmcp
Enables LLMs to interact with OpenStreetMap data through a rich set of geospatial tools, including geocoding, routing, and points of interest search.
dokku-mcp
Exposes Dokku's management capabilities through the Model Context Protocol (MCP), enabling Large Language Models (LLMs) to interact with and manage a Dokku instance.