Skip to content

Grok wiki maintainer — setup

Status (2026-06-07): Interim workflow active — talk to Grok about the personal projects wiki, then apply Grok’s summary in Cursor (commit + push). Connector setup skipped — Grok Custom MCP for GitHub exposes OAuth only (no Bearer / fine-grained PAT field).

Use case: Discuss my personal projects wiki on Grok (browser or phone), then “summarize and update the wiki” — Grok’s response becomes the edit after human review.

Goal URL: https://wiki.darcymenard.com · Repo: dmoniker/projects-wiki · Not in scope: Hermes/Crusty git, Vercel API, built-in Grok GitHub OAuth (whole account).

Active workflow (no connector)

Grok (grok.com / iOS / Android)
  → read: https://wiki.darcymenard.com in chat (no connector required)
  → discuss project(s)
  → close: “Summarize and update the wiki”
  → Grok outputs wiki update pack (files + deltas + commit message) — does NOT push

Cursor (main Mac)
  → apply edits → commit → push → Vercel redeploys wiki
  → if What-Im-Working-On.md changed materially: also update darcymenard.com/projects (separate repo)

Open a session

/wiki-maintainer
My personal projects wiki is https://wiki.darcymenard.com — let's talk about [project].

Or paste wiki/Grok-Brief.md for cold start, then name the project.

Close a session

Summarize what we discussed and output a wiki update pack:
- files under wiki/ to touch
- bullet deltas per file
- suggested commit message
Do NOT push — I will apply in Cursor.

Review in Grok → apply in Cursor → push.

Optional: /wiki-maintainer skill

Create via /skill-creator on Grok; paste grok-skills/wiki-maintainer/SKILL.md from this repo. Skill enforces propose-only until a scoped write path exists.

Blocked path — Approach A (documented for when xAI ships PAT auth)

Attempted 2026-06-07: fine-grained PAT (wiki repo only) + Custom MCP → https://api.githubcopilot.com/mcp/.

Result: After Add Connector, Grok shows OAuth credentials (Client ID, PKCE, GitHub authorize/token endpoints) — no field for Bearer / fine-grained PAT. Same blast-radius problem as the featured GitHub connector (whole-account OAuth), so do not complete that OAuth flow.

Ask sent to @xAI (public): Custom MCP connectors should accept Bearer tokens (fine-grained PATs), not only OAuth — so discuss → summarize → update works with repo-scoped git access.

When xAI adds PAT/bearer support, resume Step 1–4 below.

Step 1 — Fine-grained PAT (wiki repo only) — ready when connector supports Bearer

  1. Fine-grained tokens → Generate new token.
  2. Name: grok-wiki-mcp
  3. Repository access: Only select repositories → projects-wiki
  4. Permissions: Contents Read and write only (+ Metadata read-only automatic)
  5. Store in password manager (github_pat_…); never paste into Grok chat.

Step 2 — Custom MCP connector — blocked on Grok UI today

  1. grok.com/connectors → Custom
  2. Name: GitHub Wiki · URL: https://api.githubcopilot.com/mcp/
  3. Wait for: Bearer / PAT auth in connector UI (not OAuth-only)
  4. Do not use catalog GitHub OAuth connector

Step 3 — Skill (works today, propose-only)

grok-skills/wiki-maintainer/SKILL.md — invoke /wiki-maintainer; no GitHub connector required for read + update pack.

Step 4 — Dry run (when PAT auth lands)

Connector on + skill → propose edit → explicit push → verify https://wiki.darcymenard.com

Future options (deferred — 2026-07-18 review)

Option Repo-scoped? Host locally?
xAI adds Bearer on Custom MCP Yes (fine-grained PAT) No
GitHub App on projects-wiki + cloud MCP shim (Fly/Vercel) Yes (installation) Cloud only, not Mac
OSS repo-scoped MCP bridge Yes Optional
Interim (active) Cursor git access No

Security

  • No full-account GitHub OAuth on Grok for wiki writes.
  • Wiki-only content in wiki/ — no secrets, no Crusty operational detail.
  • Human gate: review Grok’s update pack before Cursor push.
  • Crusty / Hermes: unchanged (Aye Robot + digest only).