Mattsson
6a85efb00a
* feat(mcp): allowlist Grok's connector callback and document the Grok path Grok custom connectors self-register through /api/mcp-oauth/register with redirect_uri https://grok.com/connectors-oauth-exchange-code/, which the built-in allowlist rejected with invalid_redirect_uri before consent. Add the callback as an exact-path BUILT_IN_PATTERNS entry (trailing slash optional, no prefix) with provider 'grok', named "Grok (xAI)" on the consent page. Tests: accept, foreign-host and other-path rejection, provider mapping, and a register route test for the Grok DCR shape. Surface Grok next to ChatGPT: a "Using Grok?" side door on the onboarding Claude step (one side door open at a time, telemetry step grok), a Grok row under "Other clients" in the API & MCP settings tab using ?client=grok, and sv/en strings for both. Docs: mcp-server rule, ARCHITECTURE, README, registry entry (install section), DECISIONS. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EGbspj3hiNqvqTWZqdwysa Signed-off-by: Emil <emilmattsson14@gmail.com> * fix(mcp): cite X Corp's published Grok callback, test the consent label Review pass on #2158: the allowlist comment and DECISIONS entry claimed xAI publishes no callback and the value came from a live observation; X Corp lists https://grok.com/connectors-oauth-exchange-code/ as the "Grok (web)" redirect URL at docs.x.com/x-ads-api/mcp, and grok.com serves the path itself (slash form 308s to no-slash on the same origin). Reworded both to cite that. Adds the consent-page test for "Grok (xAI)" next to the ChatGPT one and a JSDoc on the onboarding side-door toggle. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EGbspj3hiNqvqTWZqdwysa Signed-off-by: Emil <emilmattsson14@gmail.com> --------- Signed-off-by: Emil <emilmattsson14@gmail.com> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Community Registry
This directory is the source of truth for the registry shown at gnubok.se/community/registry: skills, MCP servers, workflows and apps built on Accounted. The website syncs its registry pages from here, so adding an entry is a normal pull request against this repo.
Structure
registry/
entries/ one .mdx file per registry entry
authors/ one .mdx file per author profile
Files starting with _ are templates and are ignored by validation and sync.
Adding an entry
- Copy
entries/_template.mdxtoentries/<your-slug>.mdx. The filename is the slug and the public URL:gnubok.se/community/registry/<your-slug>. - If this is your first contribution, copy
authors/_template.mdxtoauthors/<your-handle>.mdx. Theauthorfield in your entry must match an author file, so first-time contributors add both files in the same PR. - Validate locally:
npm run validate:registry(ornpx tsx scripts/validate-registry.tswithout installing everything). - Open a PR. Commits need a DCO sign-off (
git commit -s), same as the rest of the repo; see CONTRIBUTING.md.
A maintainer reviews the entry (does it work, does it describe itself honestly, is the content safe) and merges. After merge the website pulls the entry in with its registry sync; expect it live on the site within a few days of merging.
Entry frontmatter
Required:
| Field | Type | Notes |
|---|---|---|
title |
string | Shown as the card and page title |
description |
string | Card subtitle, max 500 chars; put detail in the body |
slug |
string | Must equal the filename |
kind |
skill | mcp | workflow | app |
Which shelf it goes on |
author |
string | Handle of a file in authors/ |
status |
live | beta | archived |
Be honest; beta is fine |
lang |
sv | en |
Language of the entry body |
personas |
list | Any of founder, finance, byra, developer |
publishedAt |
date | YYYY-MM-DD |
updatedAt |
date | YYYY-MM-DD, bump when you edit |
At least one of installCommand, downloadUrl, repoUrl, externalUrl is
required so readers can actually get the thing. Optional extras:
featured (maintainer-set), oauthScopes, gnubokTools (which MCP tools it
touches), requiresWriteScope, sieCompatible, version, faq (list of
{q, a}), related (list of slugs), ogImageEyebrow.
Body rules
The body after the frontmatter is plain Markdown (headings, lists, tables,
links, fenced code blocks). The website renders bodies through MDX, which
evaluates raw tags (lowercase HTML included), {...} expressions and
import/export statements at build time, so the validator rejects all of
them. Fenced code blocks and backtick inline code are fine; they are
displayed, never executed. Need a literal <tag> or {value} in prose? Put
it in backticks.
Write the body like documentation, not a landing page: what it does, what it needs (scopes, API keys), what it will not do, and one honest limitation beats three superlatives.
What gets accepted
- It must exist and work against Accounted today (the live app or the MCP server).
- It must describe its write behavior truthfully. Anything that writes to the ledger goes through staged operations that a human approves; entries that work around that will not be listed.
- No fees are charged for listing, and your IP stays yours. Entries are documentation and are contributed under this repo's license; the thing the entry points to keeps whatever license you gave it.