Deploy an MCP server using Docker

Pull the MCP server image from Splunk AppDynamics Docker Hub:
CODE
docker pull appdynamics/appdynamics-mcp-server:latest
Example:
CODE
docker pull appdynamics/appdynamics-mcp-server:26.10.0-336
Note:

Alternatively, you can download the image from the AppDynamics Downloads portal, choose AMD64 or ARM64 to match your Docker host. Instead of docker pull, load the downloaded archive:

CODE
docker load --input "/path/to/downloaded-image.tar.gz

Use the image name and tag printed by this command in the subsequent docker run examples.

Streamable HTTP

Create appdynamics-mcp.env with non-secret server configuration:

Fixed Controller HTTP mode
The server uses one configured Controller; clients supply their credentials.
CODE
MCP_TRANSPORT=streamable-http
APPD_ENVIRONMENT=https://your-controller.example.com/controller
APPD_AUTH_MODE=request_bearer
APPD_MULTI_CONTROLLER_ENABLED=false
Multi-Controller HTTP mode
Clients share one endpoint and specify their Controller and credentials through request headers.
CODE
MCP_TRANSPORT=streamable-http
APPD_AUTH_MODE=request_bearer
APPD_MULTI_CONTROLLER_ENABLED=true
See more configurable settings for env file at Configuration reference.
MCP client configures APPD_API_TOKEN and EVENTS_API_KEY. Start the container behind a trusted local ingress or gateway:
CODE
docker run -d \
  --name appdynamics-mcp \
  --restart unless-stopped \
  --env-file appdynamics-mcp.env \
  -p 127.0.0.1:6350:6350 \
  appdynamics/appdynamics-mcp-server:latest
The local endpoints are:
CODE
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.

To terminate TLS inside the container, set both listener variables and mount the certificate files read-only, readable by the image's non-root appdynamics user:
CODE
MCP_SSL_CERTFILE=/opt/appdynamics/mcp/app/certs/tls.crt
MCP_SSL_KEYFILE=/opt/appdynamics/mcp/app/certs/tls.key
CODE
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/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.