mcpField
S
sitehost-port

sitehost-port

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

About sitehost-port

sitehost-port is an MCP server for managing Netlify sites, deploys, and builds through the Netlify REST API. It provides a core set of API operations using a personal access token rather than hosted OAuth.

Key features

  1. 01List, inspect, create, update, and delete sites
  2. 02List and inspect deploys
  3. 03Restore deploys and trigger builds
  4. 04List site builds and environment variables
  5. 05Retrieve the current user

Use cases

  1. 01Review Netlify sites and deploys
  2. 02Restore a deploy or trigger a site build
  3. 03Inspect site environment variables

MCP support

Exposes Netlify site, deploy, build, user, and environment-variable operations as MCP tools. It uses a Netlify personal access token and can run as a stdio MCP server.

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-sitehost-port": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/sitehost-port"
      ]
    }
  }
}
Run commandnpx -y @reneturcios/sitehost-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/sitehost-port0.1.0
ocighcr.io/cloudcorprecords/sitehost-port:0.1.0

Tools

12

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
namestringNoOptional site name to filter the list by.
pagenumberNoOptional page number of sites to return.
per_pagenumberNoOptional maximum number of sites to return per page.

Details

From the project README

sitehost-port

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

Tools (core subset, 12)

list_sites, get_site, create_site, update_site, delete_site, list_deploys, get_deploy, restore_deploy, trigger_site_build, list_site_builds, get_current_user, list_env_vars.

Not in this subset: forms and submissions, functions deployment and zip uploads, DNS zones and records, accounts/teams/members admin, deploy keys and SSL certificate provisioning, build hooks and build settings depth beyond name/custom_domain, split testing, Netlify Identity, large media, plugins.

Setup

Create a personal access token for your Netlify account and set it:

export NETLIFY_AUTH_TOKEN=nfp_...

Optionally override the API base with NETLIFY_API_BASE_URL (default https://api.netlify.com/api/v1). Without the token, every tool call fails with an error naming the missing variable.

CLI

npx @reneturcios/sitehost-port list_sites '{"per_page":10}'
npx @reneturcios/sitehost-port mcp        # stdio MCP server

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

MCP client config

{
  "mcpServers": {
    "sitehost-port": {
      "command": "npx",
      "args": ["-y", "@reneturcios/sitehost-port", "mcp"],
      "env": { "NETLIFY_AUTH_TOKEN": "nfp_..." }
    }
  }
}

Docker

docker run -i -e NETLIFY_AUTH_TOKEN ghcr.io/cloudcorprecords/sitehost-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.