Connect to an MCP Server to Simplify Splunk AppDynamics Operations
Connect a Model Context Protocol (MCP) server with an AI assistant to manage Virtual Appliance configuration, deployment, troubleshooting, and operations.
Connect the Model Context Protocol (MCP) server with your AI clients to centralize the configuration, deployment, troubleshooting, and management of your Virtual Appliance. This connection provides a conversational interface that streamlines complex workflows, reduces operational overhead, and improves the overall user experience.
The Virtual Appliance exposes two independent Model Context Protocol (MCP) servers under the same Virtual Appliance DNS name. Add both servers to combine platform operations with AppDynamics application and observability data.
Available MCP servers
| Server | Purpose | Client URL | Authentication |
|---|---|---|---|
| Virtual Appliance MCP | Operate and diagnose the AppDynamics Virtual Appliance. | https://VA-DNS-NAME/va-mcp |
Bearer VA-MCP-token |
| AppDynamics MCP | Query AppDynamics APM and EUM data. | https://VA-DNS-NAME/appdynamics-mcp |
Bearer AppDynamics-token |
/health and are only for connectivity checks. Do not append /mcp to either external endpoint.
Supported MCP Server Actions on Virtual Appliance
- Identify cluster nodes, namespaces, pods, services, and deployments.
- Perform pod operations.
- Detect problematic pods and monitor events.
- Monitor node and namespace resources.
- List certificates, check their validity, and apply Ingress certificates.
- Check the health of application services.
- Configure the hybrid mode.
For more information, see Available MCP Server Tools.