io.github.jyswee/sslwebsites

Registre officiel Outils de développement

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

Que pouvez-vous faire avec io.github.jyswee/sslwebsites ?

  • 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

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package sslwebsites
Claude Code
claude mcp add sslwebsites -e 'SSL_API_KEY=<your ssl_api_key>' -- npx -y sslwebsites@1.0.1
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "sslwebsites": {
            "command": "npx",
            "args": [
                "-y",
                "sslwebsites@1.0.1"
            ],
            "env": {
                "SSL_API_KEY": "<your ssl_api_key>"
            }
        }
    }
}

Variables d'environnement

  • SSL_API_KEY obligatoire secret SSLWebsites API key (ssl_free_... or ssl_live_...). Get one instantly: npx sslwebsites signup my-project --local

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. ssl
  2. See it in action
  3. Install
  4. Quick Start
  5. Certificates
  6. Monitoring — never ship an expired cert again
  7. MCP Server
  8. Billing — 7-day free trial
  9. Features
  10. Per-Project Config
  11. Agent Integration
  12. Documentation
  13. License

ssl

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

More scenarios: sslwebsites.com/#demo

Install

npm install -g sslwebsites

The npm package is sslwebsites; the command is ssl.

Quick Start

# 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).

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

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:

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.

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:

{
  "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

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.

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

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:

## 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.

Documentation

License

Proprietary - Tyga.Cloud Ltd. See LICENSE.

Questions fréquentes

Qu'est-ce que io.github.jyswee/sslwebsites ?

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

Comment installer io.github.jyswee/sslwebsites ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add sslwebsites -e 'SSL_API_KEY=<your ssl_api_key>' -- npx -y sslwebsites@1.0.1. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.jyswee/sslwebsites ?

Oui. Il attend SSL_API_KEY, à renseigner dans sa configuration.

io.github.jyswee/sslwebsites est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient io.github.jyswee/sslwebsites ?

Il est publié par jyswee. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.