Render Mcp Server

Created By
8 months ago
Overview

what is Render MCP Server?

Render's Model Context Protocol (MCP) server allows users to manage their Render infrastructure directly from compatible AI applications, such as Cursor and Claude Code.

how to use Render MCP Server?

To use the Render MCP Server, you can issue natural language prompts to perform various tasks like spinning up new services, querying databases, and analyzing metrics and logs. You can access it via the command: npx mcp-remote https://mcp.render.com/mcp.

key features of Render MCP Server?

  • Manage Render infrastructure through natural language prompts.
  • Spin up new services easily.
  • Query databases and analyze metrics and logs.

use cases of Render MCP Server?

  1. Automating the deployment of new services in a Render environment.
  2. Quickly retrieving database information without complex queries.
  3. Monitoring and analyzing application performance metrics in real-time.

FAQ from Render MCP Server?

  • What is the purpose of the Render MCP Server?

The Render MCP Server is designed to simplify infrastructure management through AI-driven commands.

  • Do I need an API key to use the Render MCP Server?

Yes, you need to provide an API key for authorization when accessing the server.

  • Can I use Render MCP Server with any AI application?

It is compatible with specific AI applications like Cursor and Claude Code.

Server Config

{
  "mcpServers": {
    "render": {
      "url": "https://mcp.render.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
Project Info
Created At
8 months ago
Updated At
8 months ago
Author Name
-
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago