{"_id":"@dearvetri/appdynamics-mcp-server","name":"@dearvetri/appdynamics-mcp-server","dist-tags":{"latest":"1.0.0"},"versions":{"1.0.0":{"name":"@dearvetri/appdynamics-mcp-server","version":"1.0.0","description":"MCP Server for AppDynamics REST API integration","type":"module","main":"dist/index.js","bin":{"appdynamics-mcp-server":"dist/index.js"},"scripts":{"build":"tsc","watch":"tsc --watch","start":"node dist/index.js","dev":"tsc && node dist/index.js"},"keywords":["mcp","appdynamics","monitoring","observability"],"author":"","license":"MIT","dependencies":{"@modelcontextprotocol/sdk":"^1.0.4","axios":"^1.6.0"},"devDependencies":{"@types/node":"^20.10.0","typescript":"^5.3.0"},"_id":"@dearvetri/appdynamics-mcp-server@1.0.0","types":"./dist/index.d.ts","_nodeVersion":"22.19.0","_npmVersion":"10.9.3","dist":{"integrity":"sha512-CxEm67epzhWwmCfi9uNlz0Dq9sfk6BdzO06l+jprkvFdmQ0KzruLom6hP+S4a2eGAapadyqX13rN8CZPE0E1+w==","shasum":"dbf63097f5eecb9e6cf1b144987d1e02c1ee1c65","tarball":"https://registry.npmjs.org/@dearvetri/appdynamics-mcp-server/-/appdynamics-mcp-server-1.0.0.tgz","fileCount":10,"unpackedSize":53070,"signatures":[{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEQCIDgZuMF5YU2QmFXnxUxx3bmsrthuVT00eqcNfncfKy3fAiBN85MajVnm1kfDe3UtWAOQ+BRZFBF5dFfBynSybURgKg=="}]},"_npmUser":{"name":"dearvetri","email":"dearvetri@gmail.com"},"directories":{},"maintainers":[{"name":"dearvetri","email":"dearvetri@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/appdynamics-mcp-server_1.0.0_1769831312427_0.15884682849585086"},"_hasShrinkwrap":false}},"time":{"created":"2026-01-31T03:48:32.302Z","1.0.0":"2026-01-31T03:48:32.571Z","modified":"2026-01-31T03:48:32.834Z"},"maintainers":[{"name":"dearvetri","email":"dearvetri@gmail.com"}],"description":"MCP Server for AppDynamics REST API integration","keywords":["mcp","appdynamics","monitoring","observability"],"license":"MIT","readme":"# AppDynamics MCP Server\n\nA Model Context Protocol (MCP) server for integrating AppDynamics with Claude Code. This allows you to query AppDynamics data directly from Claude Code for debugging production issues, analyzing metrics, and investigating errors.\n\n## Features\n\n- Query applications, nodes, tiers, and backends\n- Fetch metrics and performance data\n- Get health rule violations and alerts\n- Retrieve transaction snapshots and error details\n- Support for both Production and Non-Production environments\n\n## Prerequisites\n\n- Node.js 18 or higher\n- AppDynamics account with API access\n- Claude Code (or any MCP-compatible client)\n\n## Installation\n\n1. Install dependencies:\n```bash\ncd appdynamics-mcp-server\nnpm install\n```\n\n2. Build the TypeScript code:\n```bash\nnpm run build\n```\n\n3. Configuration is already set up at `~/.appdynamics-mcp/config.json`\n\n## Configuration\n\nYour configuration file is located at `~/.appdynamics-mcp/config.json` and contains credentials for both production and non-production environments.\n\n**Security Note:** Never commit this file to version control. The config directory is in your home folder and should have restricted permissions.\n\n## Adding to Claude Code\n\nAdd this server to your Claude Code configuration file (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS):\n\n```json\n{\n  \"mcpServers\": {\n    \"appdynamics\": {\n      \"command\": \"node\",\n      \"args\": [\n        \"/Users/vkrishnaraj/work/projects/appdynamicsclaude/appdynamics-mcp-server/dist/index.js\"\n      ]\n    }\n  }\n}\n```\n\nAfter adding the configuration, restart Claude Code.\n\n## Available Tools\n\n### 1. list_applications\nList all applications in the specified environment.\n\n**Parameters:**\n- `environment` (required): \"prod\" or \"nonprod\"\n\n**Example:**\n```\nCan you list all applications in production?\n```\n\n### 2. get_application\nGet details for a specific application.\n\n**Parameters:**\n- `environment` (required): \"prod\" or \"nonprod\"\n- `applicationName` (required): Name of the application\n\n**Example:**\n```\nGet details for the \"lftracingservice\" application in production\n```\n\n### 3. get_metrics\nGet metrics for an application.\n\n**Parameters:**\n- `environment` (required): \"prod\" or \"nonprod\"\n- `applicationName` (required): Name of the application\n- `metricPath` (required): Metric path (e.g., \"Overall Application Performance|*\")\n- `durationInMins` (optional): Duration in minutes (default: 60)\n\n**Example:**\n```\nGet performance metrics for lftracingservice in production for the last 2 hours\n```\n\n### 4. get_business_transactions\nGet business transactions for an application.\n\n**Parameters:**\n- `environment` (required): \"prod\" or \"nonprod\"\n- `applicationName` (required): Name of the application\n\n**Example:**\n```\nShow me business transactions for the agentservice application in prod\n```\n\n### 5. get_health_rule_violations\nGet health rule violations for an application.\n\n**Parameters:**\n- `environment` (required): \"prod\" or \"nonprod\"\n- `applicationName` (required): Name of the application\n- `durationInMins` (optional): Duration in minutes (default: 60)\n\n**Example:**\n```\nAre there any health rule violations for lftracingservice in production in the last hour?\n```\n\n### 6. get_snapshots\nGet transaction snapshots for an application.\n\n**Parameters:**\n- `environment` (required): \"prod\" or \"nonprod\"\n- `applicationName` (required): Name of the application\n- `durationInMins` (optional): Duration in minutes (default: 60)\n\n**Example:**\n```\nGet transaction snapshots for fraudsvc in production from the last 30 minutes\n```\n\n### 7. get_error_snapshots\nGet error snapshots for an application.\n\n**Parameters:**\n- `environment` (required): \"prod\" or \"nonprod\"\n- `applicationName` (required): Name of the application\n- `durationInMins` (optional): Duration in minutes (default: 60)\n\n**Example:**\n```\nShow me errors in the lftracingservice application in production\n```\n\n### 8. get_nodes\nGet nodes for an application.\n\n**Parameters:**\n- `environment` (required): \"prod\" or \"nonprod\"\n- `applicationName` (required): Name of the application\n\n**Example:**\n```\nWhat nodes are running for production-compliance in prod?\n```\n\n### 9. get_tiers\nGet tiers for an application.\n\n**Parameters:**\n- `environment` (required): \"prod\" or \"nonprod\"\n- `applicationName` (required): Name of the application\n\n**Example:**\n```\nShow me tiers for the lftracingservice application\n```\n\n### 10. get_backends\nGet backends for an application.\n\n**Parameters:**\n- `environment` (required): \"prod\" or \"nonprod\"\n- `applicationName` (required): Name of the application\n\n**Example:**\n```\nWhat backends does the agentservice application connect to?\n```\n\n## Usage Examples\n\nOnce configured in Claude Code, you can ask natural language questions like:\n\n- \"Show me all applications in production\"\n- \"What errors occurred in lftracingservice in the last hour?\"\n- \"Get health rule violations for fraudsvc in nonprod\"\n- \"Show me slow transactions for production-compliance\"\n- \"What's the response time for lftracingservice in the last 2 hours?\"\n\n## Troubleshooting\n\n### Server not connecting\n\n1. Check that the build completed successfully: `npm run build`\n2. Verify the path in your Claude Code config matches your actual installation path\n3. Check that config.json exists and has the correct credentials\n\n### Authentication errors\n\n1. Verify credentials in `~/.appdynamics-mcp/config.json`\n2. Test credentials by making a direct API call:\n```bash\ncurl -u \"nettracer@nettracer:garaz19xw0qr\" \\\n  \"https://nettracer.saas.appdynamics.com:443/controller/rest/applications?output=JSON\"\n```\n\n### No data returned\n\n1. Verify the application name is correct (case-sensitive)\n2. Check the time range - increase `durationInMins` if needed\n3. Ensure the application exists in the specified environment\n\n## Development\n\nTo make changes to the server:\n\n1. Edit files in `src/`\n2. Rebuild: `npm run build`\n3. Restart Claude Code\n\nFor continuous development:\n```bash\nnpm run watch\n```\n\n## Security\n\n- Configuration file contains sensitive credentials\n- Keep `~/.appdynamics-mcp/config.json` secure with appropriate file permissions\n- Never commit credentials to version control\n- Consider using environment variables or secret management for production use\n\n## License\n\nMIT\n","readmeFilename":"README.md","_rev":"1-e886127fdfcee91c019bc6942f4d177c"}