Deploy the MCP server
Deploy the MCP server by using streamable HTTP or stdio with bearer-token or OAuth authentication.
docker pull appdynamics/appdynamics-mcp-server:latest
docker pull appdynamics/appdynamics-mcp-server:26.7.0-197
Streamable HTTP
appdynamics-mcp.env with non-secret server configuration:
MCP_TRANSPORT=streamable-http
APPD_ENVIRONMENT=https://your-controller.example.com/controller
# Optional Analytics Events access. Each HTTP caller supplies its own key.
# Base origin only; do not append /events or /events/query.
# APPD_ANALYTICS_EVENTS_URL=https://analytics.api.appdynamics.com
# APPD_ANALYTICS_EVENTS_GLOBAL_ACCOUNT_NAME=your-global-account-name
APPD_API_TOKEN and EVENTS_API_KEY. Start the container behind a trusted local ingress or gateway:
docker run -d \
--name appdynamics-mcp \
--restart unless-stopped \
--env-file appdynamics-mcp.env \
-p 127.0.0.1:6350:6350 \
appdynamics-mcp-server:latest
http://127.0.0.1:6350/mcp
http://127.0.0.1:6350/health
GET /health is intentionally unauthenticated and reports process status. A successful response confirms the process is serving the route; it does not test Controller or Events connectivity.
appdynamics user:
MCP_SSL_CERTFILE=/opt/appdynamics/mcp/app/certs/tls.crt
MCP_SSL_KEYFILE=/opt/appdynamics/mcp/app/certs/tls.key
docker run -d \
--name appdynamics-mcp \
--restart unless-stopped \
--env-file appdynamics-mcp.env \
-v /approved/certificate/directory:/opt/appdynamics/mcp/app/certs:ro \
-p 127.0.0.1:6350:6350 \
appdynamics-mcp-server:latest
In stdio mode, the MCP client will start the MCP server process using the provided configuration. See Configure an MCP client.