MCP CLI

When to Use

• MCP server configuration reference
• Understanding available MCP capabilities
• Troubleshooting MCP server connections

Prerequisites

• MCP servers configured in VS Code or GitHub Copilot
• Environment variables set for authentication

Available MCP Servers

Azure MCP Server

{
  "command": "npx",
  "args": ["-y", "@anthropic/mcp-azure"],
  "env": {
    "AZURE_SUBSCRIPTION_ID": "${AZURE_SUBSCRIPTION_ID}"
  },
  "capabilities": [
    "az aks get-credentials",
    "az aks show",
    "az acr repository list",
    "az keyvault secret list",
    "az resource list"
  ]
}

GitHub MCP Server

{
  "command": "npx",
  "args": ["-y", "@anthropic/mcp-github"],
  "env": {
    "GITHUB_TOKEN": "${GITHUB_TOKEN}"
  },
  "capabilities": [
    "gh repo view",
    "gh issue list",
    "gh pr list",
    "gh workflow list"
  ]
}

Kubernetes MCP Server

{
  "command": "npx",
  "args": ["-y", "@anthropic/mcp-kubernetes"],
  "env": {
    "KUBECONFIG": "${KUBECONFIG}"
  },
  "capabilities": [
    "kubectl get",
    "kubectl describe",
    "kubectl logs",
    "kubectl apply"
  ]
}

MCP Server Access by Agent

Best Practices

1. Use environment variables for credentials
2. Create read-only variants for discovery agents
3. Document server access per agent
4. Limit capabilities per server
5. Monitor MCP server invocations

Integration with Agents

Used by: All agents with MCP configuration