MCP.so
ログイン

kuadrant-mcp-poc

@Kuadrant

kuadrant-mcp-poc について

POC for setting up Kuadrant with a mcp server running in a K8s cluster

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "kuadrant-mcp-poc": {
      "command": "docker",
      "args": [
        "build",
        "-t",
        "quay.io/${QUAY_USERNAME}/mcp-server-everything",
        "https://github.com/modelcontextprotocol/servers.git#main",
        "-f",
        "src/everything/Dockerfile"
      ]
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is kuadrant-mcp-poc?

kuadrant-mcp-poc is a proof-of-concept that deploys an MCP server with Streamable-HTTP capabilities on a Kubernetes cluster, integrating with Kuadrant for DNS, TLS, rate limiting, and authentication. It is built on the everything MCP server and targets developers testing Kuadrant with an MCP workflow.

How to use kuadrant-mcp-poc?

After meeting prerequisites (a Kubernetes cluster with Kuadrant installed), set environment variables for AWS credentials, domain, and Quay username. Build and push a Docker image for the MCP server, apply Kubernetes manifests to create the server pod, gateway, TLS, DNS, auth, and rate-limit policies. Configure VSCode Copilot as the MCP client by adding an HTTP server entry with the gateway URL and API key header (e.g., "Authorization": "APIKEY IAMALICE"). Then interact with the server through Copilot’s agent mode.

Key features of kuadrant-mcp-poc

  • Uses Streamable-HTTP transport
  • Integrates with Kuadrant for DNS, TLS, rate limiting, and auth
  • Deployable on Kubernetes via manifests
  • Based on the everything MCP server
  • Supports API key authentication via Kuadrant AuthPolicy
  • Supports rate limiting via Kuadrant RateLimitPolicy

Use cases of kuadrant-mcp-poc

  • Testing Kuadrant features (DNS, TLS, rate limiting, auth) with an MCP server
  • Deploying a secure, rate-limited MCP server on Kubernetes
  • Using VSCode Copilot as an MCP client with Streamable-HTTP transport

FAQ from kuadrant-mcp-poc

What transport does the MCP server use?

It uses Streamable-HTTP.

What dependencies are required?

A Kubernetes cluster, Kuadrant installed, AWS credentials for DNS access, a Quay account for image upload, and a root domain.

Where does the MCP server data live?

The server runs as a pod in the mcp-server namespace on the Kubernetes cluster.

Does the server support authentication and rate limiting?

Yes. The setup deploys Kuadrant AuthPolicy (with API keys) and RateLimitPolicy to enforce authentication and request rate limits.

Can I use self-signed TLS certificates with this MCP server?

No. MCP clients do not accept self-signed certificates, so a trusted certificate issuer (e.g., Let’s Encrypt) must be used.

よくある質問

What transport does the MCP server use?

It uses Streamable-HTTP.

What dependencies are required?

A Kubernetes cluster, Kuadrant installed, AWS credentials for DNS access, a Quay account for image upload, and a root domain.

Where does the MCP server data live?

The server runs as a pod in the `mcp-server` namespace on the Kubernetes cluster.

Does the server support authentication and rate limiting?

Yes. The setup deploys Kuadrant AuthPolicy (with API keys) and RateLimitPolicy to enforce authentication and request rate limits.

Can I use self-signed TLS certificates with this MCP server?

No. MCP clients do not accept self-signed certificates, so a trusted certificate issuer (e.g., Let’s Encrypt) must be used.

コメント

「その他」の他のコンテンツ