AppDynamics MCP Server 26.10.0 Adds APM Tools
Splunk's AppDynamics MCP Server Integration reached version 26.10.0 on November 3, 2026, according to the product's official changelog (Splunk). The release expands how AI applications can query and act on AppDynamics monitoring data through the Model Context Protocol, the open standard that lets AI systems connect to external tools and data sources.
New APM Tools and Prompts
The update introduces two new Application Performance Monitoring tools: one for cross-application business-transaction statistics and another for FEP (frontend performance) analysis (Splunk). Alongside the tools, AppDynamics shipped three new prompts — cross-application troubleshooting, health-rule optimization, and FEP review — designed to guide AI agents through common diagnostic workflows using the underlying data.
The documentation describes the server as an integration layer that lets AI applications interact with AppDynamics data and tools through MCP, and it emphasizes that the toolset remains read-oriented, meaning it is built for querying monitoring data across supported domains rather than making changes to production systems (Splunk).
Configuration Assessment and Deployment Changes
Version 26.10.0 also adds an optional configuration assessment feature, which is deactivated by default. Once enabled for a single APM, Browser, or Mobile application, it returns grades and supporting evidence on that application's setup (Splunk). Because the feature ships off by default, teams must explicitly turn it on before it evaluates an application.
On the infrastructure side, the server now supports both fixed-controller and multi-controller deployment modes. For multi-controller HTTP deployments, clients pass the Events URL and account information through request headers rather than static configuration, giving operators more flexibility in environments with multiple controllers (Splunk).
Installation Options Expand
Documentation for the release adds a new installation path using a Python 3.12-or-later wheel package, which sits alongside the existing Docker deployment method (Splunk). The dual installation paths give engineering teams a choice between a lightweight Python-native setup and a containerized deployment, depending on their existing infrastructure.
The release notes do not describe pricing, availability timelines beyond the release date, or customer deployment figures. Full configuration details, including the complete list of tools and prompts, are documented in AppDynamics' reference pages (Splunk).


