Files

T

Jakob Wennberg 188816652d docs(api,mcp): tool counts, changelog backfill, version-header honesty, lazy auth, endpoint map (#1929 )

Brings the developer-facing API and MCP docs back in line with origin/main
(audit 2026-08-26). Docs only; no runtime behaviour changes.

- Tool counts: the server registers 153 tools; docs said 90+/100+/120.
  All now say "150+" (connect-claude, gnubok-mcp README, plugin README,
  mcp-server rules, CLAUDE.md, registry entry with refreshed updatedAt).
  Not derived from the tools array: lib/ must not import @/extensions/.
- REST changelog: backfilled the additive 2026-08 changes (#1909 report
  date ranges + PDFs, #1864 POST /companies, #1773 vat-declarations,
  #1405 PATCH settings, #1724/#1788 customer personal_number, #1809
  cash_account_id filter). API version date unchanged.
- Version headers: Gnubok-Deprecation is planned, not emitted; the
  Gnubok-Version request header is not read today (version.ts comment,
  versioning page, conventions overlay, regenerated skills/accounted-api).
- connect-claude Path A documents lazy auth (connector works before an
  account exists; sign-in on the first company-scoped call).
- MCP server README: real Anthropic SDK call sites, real resource URIs,
  pending-operations widget, public-tools/tasks/origin-guard/pii-guard.
  Rules file gains Lazy auth + feedback/tasks paragraphs.
- api-routes endpoint map regenerated from the filesystem (560 routes,
  55 families incl. v1, agent, reconciliation account-keyed, dimensions,
  peppol, rot-rut, webshop-orders, mileage, billing, skatteverket,
  receipt-hunt).
- gnubok-mcp/accounted-mcp: /settings?tab=api is the pre-redesign URL;
  now /settings/api (README + help hints, no version bump).

Co-authored-by: Jakob Wennberg <311770904+jakobwennberg-oss@users.noreply.github.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

2026-08-26 13:35:54 +02:00

authors

feat(registry): add Bank Statement Sheet MCP server (#1472 )

2026-08-10 15:23:52 +02:00

entries

docs(api,mcp): tool counts, changelog backfill, version-header honesty, lazy auth, endpoint map (#1929 )

2026-08-26 13:35:54 +02:00

README.md

feat(registry): move community registry source of truth into the public repo (#1458 )

2026-08-08 10:54:09 +02:00

README.md

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.mdx to entries/<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.mdx to authors/<your-handle>.mdx. The author field 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 (or npx tsx scripts/validate-registry.ts without 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.