Jamf Pro MCP Server

# AI Agent Implementation Status ## Summary Created a simplified AI agent that acts as a natural language interface to the Jamf MCP server. The agent uses AWS Bedrock (Claude 3 Sonnet) to convert natural language requests into MCP tool calls. ## Architecture ### Simple Agent Design Based on user feedback: "the mcp server is doing all the work.. the agent is supposed to just be the natural language part" Key components: 1. **SimpleAgent.ts** - Minimal agent that translates natural language to single tool calls 2. **BedrockProvider.ts** - AWS Bedrock integration for Claude models 3. **MCPClient.ts** - Wrapper around MCP SDK for server communication 4. **simple-cli.ts** - Streamlined CLI interface ### Configuration - Uses AWS Bedrock with Claude 3 Sonnet model - Supports both OAuth2 and Basic Auth for Jamf API - Environment variables for all credentials ## Current Status ### Working ✅ AWS Bedrock integration with Claude 3 ✅ Natural language to tool call translation ✅ MCP server connection and tool discovery ✅ CLI interface with interactive prompt ### Issue ❌ MCP connection closes when executing searchDevices tool - Modern API returns 400 error with filter syntax - Classic API fallback might be causing process crash - Error: "MCP error -32000: Connection closed" ## Usage ```bash # Set up environment export AWS_ACCESS_KEY_ID="your-key" export AWS_SECRET_ACCESS_KEY="your-secret" export AWS_REGION="us-east-1" export JAMF_URL="https://your-instance.jamfcloud.com" export JAMF_CLIENT_ID="your-client-id" export JAMF_CLIENT_SECRET="your-client-secret" export JAMF_USERNAME="your-username" export JAMF_PASSWORD="your-password" # Run the agent npm run agent:simple # Example commands jamf> show dwight's computer jamf> list all policies jamf> get details for device 759 ``` ## Next Steps 1. Fix the Modern API filter syntax for searchDevices 2. Improve error handling to prevent MCP connection closure 3. Add retry logic for failed API calls 4. Consider removing complex agent code if simple agent works well