mcpField
A
apphost-port

apphost-port

Local
github.com/CloudCorpRecordsCloud & Infra0Updated 2w ago
Repository

About apphost-port

apphost-port is an API-key-based MCP server and CLI for managing Render services through its REST API. Its core tools cover services, deployments, environment variables, and service logs.

Key features

  1. 01List, inspect, create, update, delete, suspend, and resume services
  2. 02List deployments and retrieve deployment details
  3. 03Trigger a deployment
  4. 04List service environment variables
  5. 05Retrieve service logs

Use cases

  1. 01Review services in a Render workspace
  2. 02Trigger or inspect a service deployment
  3. 03Check configured environment variables
  4. 04Retrieve logs while investigating a service

MCP support

Exposes a core set of Render REST API operations as MCP tools. The stdio server uses a Render API key; hosted OAuth is not included.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "cloudcorprecords-apphost-port": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/apphost-port"
      ]
    }
  }
}
Run commandnpx -y @reneturcios/apphost-port

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@reneturcios/apphost-port0.1.0
ocighcr.io/cloudcorprecords/apphost-port:0.1.0

Tools

12

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
typestringNoOnly return services of this type, such as web_service.
limitnumberNoMaximum number of services to return.

Details

From the project 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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.