# Render MCP > Render MCP connects your AI agent directly to your PaaS infrastructure, letting you manage services, deployments, and scaling from conversation. Instantly list all microservices, trigger cache-clearing deploys, check live logs, or suspend worker processes without touching a dashboard. ## Overview - **Category:** ship-it - **Price:** Free - **Tags:** paas, web-hosting, deployment-automation, cdn, serverless, infrastructure-management ## Description Need to manage complex web services but hate clicking through dashboards? This MCP connects your AI agent straight into your Render account. You can treat your entire infrastructure—everything from static sites and databases to core APIs—like one single service that you talk to. Want to see what’s running? Just ask, and the agent lists every microservice on your portfolio. Need a fix for an outage? Command it to list current deployments or check live logs instantly. Scale resources up or down with simple commands, suspending workers when they aren't needed or scaling them out right before peak traffic hits. This makes managing edge infrastructure feel like talking to a teammate who already has access and knows the system inside and out. When you connect this MCP via Vinkius, your agent gains total visibility into every piece of code running on your platform. ## Tools ### create_deploy Triggers a new code deployment for a specific service. ### get_service Retrieves detailed information about a single Render service. ### list_custom_domains Lists all custom domains associated with a given service. ### list_deploys Retrieves the history of deployments for a specific service. ### list_env_vars Lists all environment variables configured for a service. ### list_services Queries and returns a comprehensive list of all services running on the account. ### resume_service Brings a suspended Render service back online. ### scale_service Increases or decreases the number of running instances for a service that supports scaling. ### suspend_service Temporarily shuts down and suspends a Render service to save resources. ## Prompt Examples **Prompt:** ``` List all running backend and logic services on my Render account. ``` **Response:** ``` I've pulled the core array. You have 3 primary services active: 'Vinkius-Engine' (srv-124, running Postgres), 'Core-API' (srv-239, running Node), and 'Static-Landing' (srv-884, running Next.js). Shall we scale the Core API? ``` **Prompt:** ``` My recent deploy on the API just failed. Start a fresh deploy now and clear the cache. ``` **Response:** ``` Understood. Firing deploy sequence for Service ID `srv-239`. The clear cache flag has been successfully appended. Deploy `dep-ab294c` has been initialized and is transitioning into 'build' phase. ``` **Prompt:** ``` Scale our main API worker down to zero instances temporarily to cut costs for the weekend. ``` **Response:** ``` Action dispatched logically. Scaling service `srv-workers-8a` down to `0` instances. Operations have halted on the target. Let me know when you desire to reinstate operations. ``` ## Capabilities ### Inventorying Services List all active services, including web apps, databases, and static sites, across your entire Render account. ### Controlling Deployments Safely kick off new deployments for specific services, or trigger a 'Clear Cache' build to ensure clean code testing. ### Managing Scaling State Scale worker instances horizontally or instantly suspend and resume background workers based on demand. ### Checking Network Config Verify custom domains attached to services and retrieve hidden environment variables for debugging. ### Monitoring Deployment History Retrieve a full list of past deployments, allowing you to check logs or roll back to stable versions. ## Use Cases ### Troubleshooting a production API outage The agent detects that the Core-API is failing. The engineer asks it to list_deploys, checks the last three builds, and realizes the cache was wrong. They then tell the MCP to run create_deploy with 'clear cache' enabled, solving the issue instantly. ### Preparing for a low-traffic holiday period The DevOps engineer tells their agent to suspend_service on all non-critical background workers and scale_service down on the main API worker. This cuts costs immediately, and they will resume everything when needed. ### Debugging a staging environment variable While coding in an unfamiliar module, the developer asks for the list_env_vars for that specific service. The MCP instantly provides the required keys, preventing them from having to ask a teammate for documentation. ### Onboarding a new team member A manager uses list_services to get an immediate inventory of all components—backend services, databases, and landing pages. This gives the new hire a complete picture without needing training on every single system. ## Benefits - Stop clicking through tabs. You can use list_services to pull up every microservice, static site, and database in a single command, giving you a full system map instantly. - Fix broken builds fast. Instead of guessing which deployment failed, you can check the history using list_deploys and verify logs without leaving your chat window. - Save money on downtime. Suspend services when they aren't needed for the weekend, then resume_service with a single command to cut costs immediately. - Test clean code easily. You don't need to wait for background processes; you can force a fresh build using create_deploy, even telling it to clear the cache. - Access sensitive settings instantly. Need to verify environment variables? list_env_vars gets those details without manual navigation through multiple security menus. ## How It Works The bottom line is you command infrastructure changes using natural language prompts instead of clicking through menus. 1. First, subscribe to this MCP and provide your Render API key. 2. Next, connect the credential to any AI-compatible client (Claude, Cursor, etc.) 3. Finally, tell your agent what needs fixing—like 'Scale the Core API up' or 'List all services'. ## Frequently Asked Questions **How do I list all my services using the Render MCP?** You ask the agent to run list_services. The MCP queries your entire account and returns a complete array of every microservice, web service, and database running under your account. **Can I force a cache-clearing deploy with Render MCP?** Yes, you can use the create_deploy tool. By specifying the 'Clear Cache' flag in your request to create_deploy, you ensure that the new deployment uses the freshest code and avoids old cached assets. **What is the difference between suspend_service and scale_service?** Suspension (suspend_service) completely halts a service's operation to save costs. Scaling (scale_service) adjusts the number of running instances while keeping the service operational. **Can I check environment variables with Render MCP?** Absolutely. The list_env_vars tool lets you query and retrieve all hidden environment variables for any specific service, which is crucial for debugging connections or keys. **Does Render MCP help me debug a failed deployment?** Yes. You can use list_deploys to view the history of deployments and get the necessary logs to pinpoint exactly when and why a specific version failed.