Sslwebsites

io.github.jysweePublished by GitHub account jysweev1.0.1Updated Oct 24, 2026

SSL certificate management for coding agents. Issue, renew, monitor certs. 10 tools stdio.

The publisher's own server: Vips

Overview

AI-generated overview

A local MCP server that lets a coding agent issue, renew, revoke, download and monitor SSL/TLS certificates through the SSLWebsites service.

What you can do
Check project status, certificate health and certificates expiring within a given number of days, and list or show certificate details. Issue single or bulk certificates for domains, renew or revoke existing ones, and download a certificate bundle. Retrieve server-specific installation guides for nginx, Apache, IIS, cPanel, Plesk, Tomcat, AWS ELB, Cloudflare and Heroku. Configure webhooks so certificate events notify an external endpoint.
When to use it
Useful when an agent deploys or maintains websites and should manage their TLS certificates itself, including catching expiries before browsers show warnings. Suited to teams that want certificate issuance and renewal driven from Claude Code, Cursor, Cline, Windsurf, Aider, Codex or another MCP client.
Requirements
Runs locally over stdio via the npm package sslwebsites (command ssl mcp-serve), so Node.js and npx are needed. Requires an SSLWebsites API key supplied through the SSL_API_KEY environment variable; a free-plan key can be created with the signup command. Network access to the SSLWebsites service is required.
Before you install
The API key is a secret and should be kept out of version control; the README advises adding the .ssl config directory to .gitignore. Revoking a certificate is described as irreversible. Paid plans start a 7-day free trial with a first charge on day 7, and the agent can produce a checkout link for a human to open. Webhooks send certificate event data to an external URL you configure.

Installation

In SourceWeft

  1. Open Sslwebsites in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ssl

[npm version] [MCP] [smithery badge]

SSL certificate management for coding agents. Issue, renew, monitor certs — as easy as git.

git for your code. ssl for your certs.

Your agent ships the site — then the cert expires three months later and nobody notices until the browser warning. SSLWebsites is the certificate manager your agent runs itself: one install, and it issues, renews, and monitors its own certs — with install guides for nine server types and expiry alerts before anything breaks.

Works with: Claude Code · Cursor · Cline · Windsurf · Aider · Codex · any MCP client

See it in action

Real terminal sessions stitched with the human dashboard — no mockups. Click a poster to watch.

Signup to issued certMonitor & renewUpgrade to paid
[Signup to issued cert][Monitor & renew][Upgrade to paid]

More scenarios: sslwebsites.com/#demo

Install

bash
npm install -g sslwebsites

The npm package is sslwebsites; the command is ssl.

Quick Start

bash
# Create a project — API key active instantly, free planssl signup my-project --local
# Issue a certificatessl cert example.com
# What needs attention?ssl statusssl expiring
# Renew before it bitesssl cert renew CERT-ID
# Server-specific install guidessl cert install CERT-ID --server nginx
# Full referencessl --help

Signup also returns a claim link — hand it to your human and they get the web dashboard for the same project (they set a password, you keep the API key).

Certificates

CommandDescription
ssl cert <domain>Issue certificate
ssl certsList certificates
ssl cert show <id>Certificate detail
ssl cert renew <id>Renew certificate
ssl cert revoke <id>Revoke (irreversible)
ssl cert download <id>Download ZIP bundle
ssl cert install <id> --server nginxInstall guide (nginx, apache, iis, cpanel, plesk, tomcat, aws-elb, cloudflare, heroku)
ssl cert bulk domains.txtBulk create

Monitoring — never ship an expired cert again

bash
ssl status              # project overview: active / expiring / expiredssl health              # certificate health aggregatessl expiring --days 14  # what needs attention

Add webhooks and your stack gets notified instead of polling:

bash
ssl webhook set https://your-stack.example/hooksssl webhooks

MCP Server

Prefer tools over a CLI? ssl ships an MCP server. Point Claude Code (or any MCP client) at it and your agent gets 10 native tools: status, list, show, create, renew, revoke, download, expiring, health, install guides.

bash
claude mcp add sslwebsites -- ssl mcp-serve

For clients that use a JSON config (Cline, Cursor, Windsurf), pass your API key via the SSL_API_KEY environment variable:

json
{  "mcpServers": {    "sslwebsites": {      "command": "ssl",      "args": ["mcp-serve"],      "env": { "SSL_API_KEY": "ssl_free_your_key_here" }    }  }}

No key yet? ssl signup my-project --local provisions one instantly — free plan, no card.

Billing — 7-day free trial

bash
ssl billing                   # plans + upgrade linkssl billing upgrade basic     # checkout URL for the human to openssl billing verify SUB_ID     # trial verified? card attached?

$0 today, first charge on day 7, cancel anytime. The agent gets the checkout URL; the human opens it.

Features

  • Certificates — issue, renew, revoke, download, bulk create
  • Monitoring — expiry tracking, health aggregate, ssl expiring before it breaks
  • Install guides — nine server types, copy-paste ready
  • Webhooks — HTTP callbacks on certificate events
  • Claim links — agent signs up, human claims the dashboard; one project, two interfaces
  • MCP server — 10 tools via ssl mcp-serve: Claude Code, Cursor, any MCP client
  • Agent schema — ssl init --agent-schema returns every command + valid flags as JSON

Pricing: free plan with instant API key. Paid plans start with a 7-day free trial. Details.

Per-Project Config

bash
ssl login --local --key YOUR_KEY    # saves to .ssl/config.json (project-local)ssl config                          # show active config

Config is per-project and auto-loaded from .ssl/config.json. Add .ssl/ to your .gitignore.

Priority: --key flag → SSL_API_KEY env → SSLWEBSITES_API_KEY env → .ssl/config.json → ~/.ssl/config.json.

Agent Integration

Add to your CLAUDE.md, .cursorrules, .clinerules, .windsurfrules, or AGENTS.md:

## SSLWebsitesThis project uses the ssl CLI for certificate management.Config is in .ssl/config.json (auto-loaded).If not configured: ssl login --local --key YOUR_KEY
Run `ssl init --agent-schema` — it returns every command + valid flags.This is the single source of truth: if it is not in the schema, do not use it.

Documentation

License

Proprietary - Tyga.Cloud Ltd. See LICENSE.

Source: README.md at commit f2dade6

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Vipsallowed integrations