Add WhatSetter plugin

[devlikemasta]

What this adds

content/plugins/whatsetter.md — WhatSetter (plugin), an AI appointment setter on WhatsApp that a Grok Bot drives over a hosted MCP server.

Checklist

• This PR adds exactly ONE new file under content/ (plus assets for this entry, if any).
• It follows CONTRIBUTING.md — required fields + the golden rules (G1–G8).
• npm run validate passes locally (schema, slug, vocabularies).
• slug is kebab-case and exactly matches the filename.
• I ran / used this myself end to end — it works today.
• Every URL in the frontmatter resolves to real, relevant content.
• The prompt body is the real, complete prompt — not a summary or a teaser.
• The entry body is plain markdown — no raw HTML.
• I did NOT set verified_at or status: live.
• This is not an ad.
• author is us: this is our own plugin, so there is no scouted_by.
• I license this contribution under CC BY 4.0 (attribution: entry author + grokbot.dev).

Where it came from

We build WhatSetter and we wrote this plugin. The source repo is our organization's own, MIT, published on 2026-09-12: https://github.com/whatsetter/whatsetter-plugin

Tool reference and install docs: https://docs.whatsetter.com/developers/mcp/

How it was verified: the hosted MCP server is live and in production use. We exercised the full flow (OAuth consent page, whoami, read-only briefing, campaign pause and resume) from MCP clients that support Streamable HTTP with OAuth 2.1 discovery, and the same manifest is submitted to the Cursor and xAI catalogs. Nothing in the entry describes a capability the server does not expose today.

Two optional fields are left out on purpose rather than guessed: x_handle and founder. Happy to add them in a follow-up if you would like them filled.

[scheemunai]

Merged into main (7f1b60f) and live now: https://grokbot.dev/plugins/whatsetter/

Verified before merging: whatsetter.com and docs.whatsetter.com/developers/mcp/ both resolve, the MCP endpoint at mcp.whatsetter.com/mcp answers (401 unauthenticated, as expected for an OAuth-gated server), and the source repo whatsetter/whatsetter-plugin is the MIT one described in your notes.

Thanks in particular for:

• The safety rails baked into the prompt — explicit approval before every send/write, no cold outreach to never-contacted numbers, quota respect, and idempotent sends. That is exactly how we want write-capable plugins to behave.
• Leaving x_handle and founder out rather than guessing. Correct call.

Maintainer edits on merge: status: live and verified_at: 2026-09-21T11:02:12Z (these are maintainer-set fields, so please don't set them in future PRs).

One note for next time: updated_at is normally left at the date of the content change rather than bumped to the merge time — cosmetic only, and I've set it to the verification timestamp here. Welcome aboard, and glad to have WhatSetter listed.