← ClaudeAtlas

rudder-environment-checklisted

Checks RudderStack tool prerequisites and reports status. Use when checking prerequisites, setup status, what tools are missing, or before running RudderStack workflows for the first time
rudderlabs/rudder-agent-skills · ★ 19 · AI & Automation · score 77
Install: claude install-skill rudderlabs/rudder-agent-skills
# RudderStack Environment Check Quick diagnostic that checks all RudderStack tool prerequisites and provides actionable guidance. ## When to Use - Before starting with RudderStack workflows - When troubleshooting "command not found" errors - To verify your development environment is ready ## Check Process Run these checks in sequence: ### 1. Check rudder-cli ```bash # Check if installed which rudder-cli # If installed, check authentication rudder-cli workspace info ``` ### 2. Check Terraform (if using terraform workflows) ```bash # Check if installed which terraform # If installed, check version terraform version # Check if provider is configured (run in project directory) terraform providers ``` ### 3. Check MCP Server Connectivity ```bash # Check if hosted MCP server is reachable curl -s -o /dev/null -w "%{http_code}" https://mcp.rudderstack.com/health ``` ### 4. Check the MCP tools Check that the rudderstack MCP server's tools `list_sources` and `get_source` are available to you. Don't call them. Both routes have them, the OAuth one at `/mcp` and the access-token one at `/bearer-auth-mcp`; `user_details` is on the OAuth route only. They are missing when no RudderStack server is added, when it is disabled, or when the user has not signed in to it. If they are missing, connect the server that is there before adding one. In Claude Code, `claude mcp list` prints each server's name and URL, and a RudderStack server can have any name; the rudder-core plugin's is