Add Jobkeepr plugin entry

[dandyer]

What this adds

Jobkeepr (plugin) — field service management software for small contractor crews, with a hosted MCP server at https://jobkeepr.com/mcp.

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.
• If this is someone else's work — n/a, this is my own product, submitted as author.
• I license this contribution under CC BY 4.0.

Where it came from

I build Jobkeepr and I run a TV mounting business on it, so this is a first-party listing rather than a scouted one. Flagging that openly since self-submissions deserve extra scrutiny under G6.

Verifiable now:

• Hosted endpoint: https://jobkeepr.com/mcp (Streamable HTTP). Unauthenticated initialize returns 401; https://jobkeepr.com/.well-known/oauth-authorization-server returns 200. OAuth 2.1 + PKCE, no API key to paste.
• Official MCP registry: com.jobkeepr/jobkeepr v1.0.0, status active.
• Source, MIT: https://github.com/dandyer/jobkeepr-mcp

Two things I deliberately wrote into the entry because they are the honest shape of the tool, not selling points:

1. No tool here can text a customer. SMS is excluded from the surface on purpose — it is the one action that reaches a real person and cannot be undone. The bot drafts, the human sends.
2. Writes land immediately, no staging and no undo, so the prompt makes the bot show exactly what it is about to create, reschedule, cancel or close and wait for a go-ahead. close_jobs can act on many jobs at once, so it reads the full set back first.

Happy to cut the entry down, move it to a different category/subcategory pair (work/scheduling was my read; finance-ops/invoicing and sales/crm were the alternatives), or drop it entirely if first-party listings aren't wanted here.

🤖 Generated with Claude Code

[scheemunai]

Merged into main (commit e8d837e) and live now: https://grokbot.dev/plugins/jobkeepr/

Verification I ran before merging: jobkeepr.com 200, the hosted endpoint at https://jobkeepr.com/mcp responds (405 on GET, as a Streamable-HTTP POST endpoint should), and the repo README corroborates every install step you wrote — the OAuth 2.1 + PKCE remote connect, the npx -y github:dandyer/jobkeepr-mcp stdio path with JOBKEEPR_API_KEY, the "not on npm" caveat, the read/write tool split, the per-tool permission model, and the deliberate absence of SMS. The pricing line matches the site ($39/mo, $10/mo per additional user, 14-day trial, no card).

Two maintainer-only edits, which is the only reason this needed a reviewer at all:

• status: proposed → status: live
• added verified_at: "2026-09-03T17:01:57Z"

Nothing else changed — no schema fixes were needed. Everything landed inside limits (tagline 84/90, pricing_note 108/120, longest install step 241/300) and work / scheduling is a valid category pair.

Worth saying plainly: the prompt is the best-gated submission I've reviewed in a while. It shows the exact change before any create/reschedule/cancel/close and waits for a go-ahead, and it reads the full set back before a bulk close_jobs — which is the right instinct for a tool surface with immediate writes and no undo. Excluding SMS from the tool surface entirely, rather than gating it, is the correct call and I've left that reasoning visible on the page.

Thanks for a listing that was accurate end to end. Full build gate passed and it's deployed.