MCP Tools Reference — All Platform Services

For agents starting new projects: This is your complete guide to all MCP tool servers available on the BlueFly platform. Use these to wire tools into kagent agents, Claude Code, Cursor, or any MCP-compatible client.

Quick Reference

External Access (NodePort)

For clients outside the k3s cluster (e.g., Claude Code on Mac, Cursor):

---

1. kagent-tool-server (113 tools)

What: The main kagent tool server bundled with kagent 0.7.17. Provides Kubernetes, Helm, Cilium, Istio, Argo Rollouts, and Prometheus tools.

Internal URL: http://kagent-tools.kagent:8084/mcp External URL: http://oracle-platform.tailcf98b3.ts.net:30084/mcp Protocol: Streamable HTTP Image: ghcr.io/kagent-dev/kagent/tools:0.0.13

Tool Categories

kagent Agent Wiring

# In a kagent Agent spec (v1alpha2):
spec:
  type: Declarative
  declarative:
    tools:
    - type: McpServer
      mcpServer:
        name: kagent-tool-server
        kind: RemoteMCPServer
        toolNames:
        - k8s_get_resources
        - k8s_get_pod_logs
        - k8s_apply_manifest
        - k8s_describe_resource
        - helm_list_releases
        - helm_upgrade
        - prometheus_query_tool

Claude Code / Cursor Config

{
  "mcpServers": {
    "kagent-tools": {
      "type": "http",
      "url": "http://oracle-platform.tailcf98b3.ts.net:30084/mcp"
    }
  }
}

---

2. kagent-grafana-mcp (54 tools)

What: Grafana MCP server — provides alerting, dashboard, annotation, incident, and datasource tools.

Internal URL: http://kagent-grafana-mcp.kagent:8000/mcp External URL: http://oracle-platform.tailcf98b3.ts.net:30800/mcp Protocol: Streamable HTTP Image: mcp/grafana:latest

Required Environment Variables

Creating a Grafana Service Account Token

# From Oracle:
GRAFANA_IP=$(kubectl get svc -n monitoring kube-prometheus-stack-grafana -o jsonpath='{.spec.clusterIP}')
# Create service account
curl -s -u admin:<password> http://${GRAFANA_IP}:80/api/serviceaccounts \
  -X POST -H "Content-Type: application/json" \
  -d '{"name":"kagent-mcp","role":"Admin"}'
# Create token (use the id from above)
curl -s -u admin:<password> http://${GRAFANA_IP}:80/api/serviceaccounts/<id>/tokens \
  -X POST -H "Content-Type: application/json" \
  -d '{"name":"kagent-token"}'

Tool Categories

kagent Agent Wiring

tools:
- type: McpServer
  mcpServer:
    name: kagent-grafana-mcp
    kind: RemoteMCPServer
    toolNames:
    - search_dashboards
    - query_prometheus
    - list_alert_rules
    - create_annotation
    - list_incidents

---

3. GKG — Knowledge Graph (8 tools)

What: BlueFly Graph Knowledge Graph — semantic search, entity management, relationship mapping.

URL: https://gkg.bluefly.internal/mcp/sse Protocol: SSE (Server-Sent Events) Auth: None (public, tunneled through Cloudflare)

kagent Agent Wiring

# NOTE: GKG is in gitlab-agent namespace, not kagent
# The RemoteMCPServer exists as gitlab-agent/gkg
tools:
- type: McpServer
  mcpServer:
    name: gkg
    kind: RemoteMCPServer
    namespace: gitlab-agent  # cross-namespace reference
    toolNames:
    - search
    - get_entity
    - list_entities

Claude Code / Cursor Config

{
  "mcpServers": {
    "gkg": {
      "type": "sse",
      "url": "https://gkg.bluefly.internal/mcp/sse"
    }
  }
}

---

4. kagent-querydoc (1 tool)

What: Document Q&A — doc2vec-based document search and question answering.

Internal URL: http://kagent-querydoc.kagent:8080/mcp Protocol: Streamable HTTP Image: ghcr.io/kagent-dev/doc2vec/mcp:1.1.14

Tools

---

5. GitLab MCP (built-in, 15 tools)

What: GitLab's native MCP server. Built into GitLab.com. Provides issue, MR, pipeline, and search tools with full OAuth 2.0 auth.

URL: https://gitlab.com/api/v4/mcp Protocol: HTTP (recommended) or stdio via npx mcp-remote Auth: OAuth 2.0 Dynamic Client Registration (automatic) Requirements: GitLab Premium/Ultimate, Duo features enabled

Tools

Claude Code Setup

claude mcp add --transport http GitLab https://gitlab.com/api/v4/mcp

Cursor Setup

Settings > Cursor Settings > Tools & MCP > Add:

{
  "mcpServers": {
    "GitLab": {
      "type": "http",
      "url": "https://gitlab.com/api/v4/mcp"
    }
  }
}

stdio (for Claude Desktop, Zed, Continue)

{
  "mcpServers": {
    "GitLab": {
      "command": "npx",
      "args": ["mcp-remote", "https://gitlab.com/api/v4/mcp"]
    }
  }
}

Wiring into kagent

To use GitLab MCP in kagent, you need to register it as a RemoteMCPServer. Since it requires OAuth, this currently does NOT work directly from kagent controller (no OAuth flow). Options:

1. Use npx mcp-remote as a sidecar/bridge
2. Use a PAT-based proxy
3. Use the glab CLI via kagent-tool-server's shell tool

---

Wiring Tools into kagent Agents

RemoteMCPServer CRD

apiVersion: kagent.dev/v1alpha2
kind: RemoteMCPServer
metadata:
  name: my-mcp-server
  namespace: kagent
spec:
  url: "http://my-service.kagent:8080/mcp"
  protocol: STREAMABLE_HTTP  # or SSE
  description: "My custom MCP server"
  timeout: "30s"
  sseReadTimeout: "5m0s"
  terminateOnClose: true

Agent Tool Reference

apiVersion: kagent.dev/v1alpha2
kind: Agent
metadata:
  name: my-agent
  namespace: kagent
spec:
  type: Declarative
  declarative:
    modelConfig: gpt4o
    systemMessage: "You are a helpful agent..."
    tools:
    - type: McpServer
      mcpServer:
        name: kagent-tool-server     # RemoteMCPServer name
        kind: RemoteMCPServer
        toolNames:                   # Specific tools (from discoveredTools)
        - k8s_get_resources
        - k8s_get_pod_logs
    - type: McpServer
      mcpServer:
        name: kagent-grafana-mcp
        kind: RemoteMCPServer
        toolNames:
        - search_dashboards
        - query_prometheus

How Tool Discovery Works

1. Create a RemoteMCPServer CR pointing to the MCP server URL
2. kagent controller connects, fetches tool list → stored in status.discoveredTools
3. Agent references specific toolNames from the discovered list
4. At runtime, agent calls tools via the controller → MCP server

---

Drupal Tool API Integration

Drupal → kagent (Drupal tools available to kagent agents)

Create a Drupal MCP server module that exposes Drupal operations as MCP tools:

# Register as RemoteMCPServer
apiVersion: kagent.dev/v1alpha2
kind: RemoteMCPServer
metadata:
  name: drupal-tools
  namespace: kagent
spec:
  url: "https://marketplace.blueflyagents.com/api/mcp"  # Drupal MCP endpoint
  protocol: STREAMABLE_HTTP
  description: "Drupal AgentDash tools"

Drupal module would expose tools like:

• drupal_list_content — list/search Drupal content
• drupal_create_node — create content
• drupal_get_agent_status — agent marketplace status
• drupal_deploy_recipe — deploy a Drupal recipe

kagent → Drupal (kagent status/tools visible in Drupal)

Drupal module polls kagent API for:

• Agent list: GET /api/agents?namespace=kagent
• Agent status: GET /api/agents/{name}?namespace=kagent
• MCP servers: GET /api/remotemcpservers?namespace=kagent
• Tool list per server: parsed from RemoteMCPServer status

API base: https://kagent.blueflyagents.com (port 30083)

---

Current State (2026-02-26)

ModelConfigs (all agents currently on OpenAI)