Back to Browse

Apphost Port MCP Server

Developer ToolsUse Caution4.8MCP RegistryLocal
Free

Server data from the Official MCP Registry

Render services, deploys, env vars and logs as MCP tools.

About

Render services, deploys, env vars and logs as MCP tools.

Security Report

4.8
Use Caution4.8High Risk

apphost-port is a clean, API-key-authenticated REST client for the Render API with no exfiltration, shell execution, or hardcoded secrets, and its network and env var access matches its purpose. The main concerns are that list_env_vars and list_service_logs can surface secret values into the AI context, and that destructive tools (delete_service, trigger_deploy, suspend_service) run without confirmation, so users should scope the API key carefully. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 11 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

RENDER_API_KEYRequired

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-cloudcorprecords-apphost-port": {
      "env": {
        "RENDER_API_KEY": "your-render-api-key-here"
      },
      "args": [
        "-y",
        "@reneturcios/apphost-port"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

apphost-port

Render services as MCP tools, talking to the Render REST API. apphost-port is a clean-room rebuild of the core surface of the Render MCP server, under a new name: fresh code, no copied branding. The original is Render's official hosted MCP (remote/OAuth); hosted OAuth is NOT reproduced — this rebuild is an API-key REST client for the same API.

Tools (core subset, 12)

list_services, get_service, create_service, update_service, delete_service, suspend_service, resume_service, list_deploys, get_deploy, trigger_deploy, list_env_vars, list_service_logs.

Not in this subset: static sites / cron jobs / background workers creation depth beyond the generic create_service, Postgres and Key Value (Redis-compatible) data services, disks, blueprints/IaC sync, metrics depth, log streams/sinks, custom domains management, team/user admin, billing, deploy hooks and webhooks admin, SSH/shell access.

Setup

Create an API key in your Render dashboard and set it:

export RENDER_API_KEY=rnd_...

Optionally override the API base with RENDER_API_BASE_URL (default https://api.render.com/v1). Without the key, every tool call fails with an error naming the missing variable. create_service requires the workspace owner_id and defaults the service type to web_service.

CLI

npx @reneturcios/apphost-port list_services '{"limit":10}'
npx @reneturcios/apphost-port mcp        # stdio MCP server

Each tool name is a subcommand taking one JSON object argument.

MCP client config

{
  "mcpServers": {
    "apphost-port": {
      "command": "npx",
      "args": ["-y", "@reneturcios/apphost-port", "mcp"],
      "env": { "RENDER_API_KEY": "rnd_..." }
    }
  }
}

Docker

docker run -i -e RENDER_API_KEY ghcr.io/cloudcorprecords/apphost-port

Development

npm install
npm run build
npm test

License

MIT

Reviews

No reviews yet

Be the first to review this server!