SSLWebsites provides SSL certificate management for coding agents. It focuses on issuing, renewing, and monitoring certificates for sites shipped by an agent, addressing the issue of certificates expiring months later without notice. The server exposes MCP functionality via standard I/O and includes 10 tools.
π οΈ Key Features
Issue SSL certificates
Renew existing certificates
Monitor certificate status
10 tools via stdio
π Use Cases
Manage certificates for sites deployed by coding agents
Avoid browser warnings caused by certificates expiring after delivery
β‘ Developer Benefits
Certificate management as part of an agent workflow
Tool-based access (10 MCP tools) through stdio
β οΈ Limitations
Documentation excerpt provided does not list specific domains, integrations, or monitoring depth beyond βmonitor certs.β
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.
The npm package is sslwebsites; the command is ssl.
Quick Start
bash
# Create a project β API key active instantly, free plan
ssl signup my-project --local# Issue a certificate
ssl cert example.com
# What needs attention?
ssl status
ssl expiring
# Renew before it bites
ssl cert renew CERT-ID
# Server-specific install guide
ssl cert install CERT-ID --server nginx
# Full reference
ssl --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).
ssl status # project overview: active / expiring / expired
ssl health # certificate health aggregate
ssl expiring --days 14 # what needs attention
Add webhooks and your stack gets notified instead of polling:
bash
ssl webhook set https://your-stack.example/hooks
ssl 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:
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 link
ssl billing upgrade basic # checkout URL for the human to open
ssl 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.
Add to your CLAUDE.md, .cursorrules, .clinerules, .windsurfrules, or AGENTS.md:
code
## SSLWebsites
This 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.