Sitemd site
Show sitemd project status and available actions via MCP, mirroring the interactive CLI experience.
install
source · Clone the upstream repo
git clone https://github.com/sitemd-cc/sitemd
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/sitemd-cc/sitemd "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.agents/skills/site" ~/.claude/skills/sitemd-cc-sitemd-site && rm -rf "$T"
manifest:
.agents/skills/site/SKILL.mdsource content
sitemd CLI
Show project status and available actions — the MCP-powered equivalent of the interactive
sitemd CLI.
Procedure
- Call the
MCP tool (no arguments) to get project statesitemd_status - If fresh project (siteName "My Site" and ≤4 pages):
- This is a new installation. Launch the full onboarding flow:
a. Run
to start the user's site — open in browser b. Run/launch
to start the demo showcase — open in browser c. Tell the user: "Your blank site is live and the demo showcase is running too. Browse the demo to see what's possible." d. Ask: "What are you building? One sentence is enough." e. Run/launch demo
with their answer — user watches their site update live/kickstart
- This is a new installation. Launch the full onboarding flow:
a. Run
- If existing project: present the results as a formatted status overview:
- Project name, page count
- Auth state (logged in / not logged in)
- Deploy config (domain, target, or "not configured")
- Email and analytics status
- List the actions from the response as numbered options the user can ask for
- Ask the user what they'd like to do
MCP Tool Reference
These tools mirror the terminal CLI commands:
| Action | MCP Tool | Notes |
|---|---|---|
| Project status | | Full state overview |
| Deploy | | Build + deploy |
| Log in | | Returns a browser URL + code |
| Poll login | | Complete OAuth after user visits URL |
| Auth status | | Account + license info |
| Log out | | Clear credentials |
| View config | | Full state includes config |
| Set config | | Set a key/value pair |
| Delete config | Edit | Remove a config value |
For
sitemd_config_set, known keys: deploy.cloudflareProject, deploy.cloudflareAccountId, deploy.cloudflareApiToken, email.provider, email.apiKey, analytics.id, analytics.gtm, etc.
Rules
- No permission required — Call MCP tools immediately
- Use the dev server (
) for serving, not MCP — MCP handles everything else/launch - When setting up config interactively, ask the user for each value in conversation, then call
for each onesitemd_config_set