Files

T

Jakob WennbergandClaude Opus 4.8 7aa37fd3b8 fix(mcp): return 405 (not 401) on GET /mcp to stop client re-auth storm (#747 )

The Streamable HTTP GET handler returned 401 unconditionally. This server is
stateless and offers no server-initiated SSE stream, for which the MCP
Streamable HTTP spec requires 405 Method Not Allowed.

Returning 401 made spec-compliant clients (Claude connector, Claude Desktop,
Cursor) treat the SSE GET as an auth failure and enter a refresh-token →
re-open-GET → 401 retry loop. Across the active connector base this storms
/api/extensions/ext/mcp-server/mcp (observed ~steady GET→401 traffic on
app.gnubok.se) and churns OAuth API-key rotation — and tripped a Vercel
usage anomaly (edge requests + function invocations spiking ~16x).

OAuth discovery remains bootstrapped on the POST 401 (WWW-Authenticate +
.well-known/oauth-protected-resource); the POST JSON-RPC channel and the
POST-only npm bridge are unaffected.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-17 14:26:13 +02:00

__tests__

Bug/year end numbers (#744 )

2026-06-16 18:22:09 +02:00

prompts

Accounted rebrand + swarm-skill cleanup + bank-reconciliation fixes (#643 )

2026-06-03 10:52:01 +02:00

resources

Accounted rebrand + swarm-skill cleanup + bank-reconciliation fixes (#643 )

2026-06-03 10:52:01 +02:00

skills

Accounted rebrand + swarm-skill cleanup + bank-reconciliation fixes (#643 )

2026-06-03 10:52:01 +02:00

widgets

Accounted rebrand + swarm-skill cleanup + bank-reconciliation fixes (#643 )

2026-06-03 10:52:01 +02:00

index.ts

fix(mcp): return 405 (not 401) on GET /mcp to stop client re-auth storm (#747 )

2026-06-17 14:26:13 +02:00

manifest.json

feat: MCP server, API keys, OAuth, and KPI dashboard (#72 )

2026-03-21 12:57:14 +01:00

origin-guard.ts

feat(mcp): Origin-header validation + serverInfo title + connect-claude docs export (P0-4 follow-up) (#684 )

2026-06-08 09:14:46 +02:00

README.md

feat(mcp): tool titles + Connect-with-Claude docs for Connectors Directory readiness (P0-4) (#682 )

2026-06-06 11:47:21 +02:00

server.ts

Bug/year end numbers (#744 )

2026-06-16 18:22:09 +02:00

tool-result.ts

Add/ai native supp (#385 )

2026-05-04 11:12:29 +02:00

README.md

Accounted MCP server

JSON-RPC 2.0 server exposing the Accounted bookkeeping engine to MCP clients (Claude Desktop, Claude Code, etc.). Endpoint: /api/extensions/ext/mcp-server/mcp. OAuth and stdio bridge live alongside the API surface — see app/api/mcp-oauth/ and packages/gnubok-mcp/.

Tool authoring contract

Enforced by tests in __tests__/ — these are not style preferences, they're guard rails.

additionalProperties: false on every inputSchema. Guarded by strict-schemas.test.ts. Forces clear rejections on hallucinated fields instead of silent ignores.
Descriptions ≤ 280 chars. Guarded by output-schema.test.ts. No Args: / Returns: / Examples: prose — those belong in JSON Schema. Use agent-native hints ("Use to…", "Call X first", "HIGH risk").
Staged-operation envelope for write tools — outputSchema: STAGED_OPERATION_SCHEMA (server.ts). Fields: staged, risk_level, actor, message, preview, period_status?, next?. The staged: true boolean is the explicit completion signal; agents must not infer completion from prose. Do NOT introduce a parallel { success, shouldContinue, output } envelope.
period_status threading — any tool that ties to a fiscal-period-bound date (categorize, mark paid, create voucher, correct/reverse entry, approve supplier invoice) passes dateForPeriodCheck to stagePendingOperation. Response then includes period_status: { period_id, status: open|locked|closed, lock_date } so widgets and agents disable writes without round-trips.
Scope mapping — every new tool needs an entry in lib/auth/api-keys.ts TOOL_SCOPE_MAP. Missing entries default to deny.
Tests for new write tools — add staging-gate coverage to __tests__/voucher-tools.test.ts (or a sibling) plus executor coverage to lib/pending-operations/__tests__/voucher-executors.test.ts if the tool stages a new operation_type.

Determinism / cache stability

Tool definitions (name, description, inputSchema, outputSchema, annotations) are declared as static object literals at module load — no timestamps, no UUIDs, no Date/Math.random in the definition layer. This makes the tools/list JSON payload byte-stable across requests, which lets agent-side prompt caches stay warm. Do not introduce per-request non-determinism into the definitions block. Anything time-bound or random belongs inside execute().

For internal Anthropic API usage (today only extensions/general/invoice-inbox/lib/extract-invoice-fields.ts): annotate stable prefixes with cache_control: { type: 'ephemeral' } and log usage.cache_read_input_tokens for hit-ratio observability. The 1h TTL from the agent-native API plan (item 10) requires the direct Anthropic API; Accounted's Bedrock path defaults to a shorter TTL.

Payload-size watchdog

payload-size.bench.test.ts enforces a tools/list JSON payload ceiling (currently 36,000 tokens — bumped from 32,000 when top-level Tool.title landed on all tools for Claude Connectors Directory readiness). If the test fires, the right answer is rarely "raise the ceiling" — instead, trim descriptions or leverage gnubok_search_tools (already deployed; tool definitions can defer to it for discovery rather than enumerating in tools/list).

Where things live

server.ts — the tools array + JSON-RPC dispatcher
tool-result.ts — withNext(), toToolError() response helpers
resources/ — read-only Accounted:// URIs (active company, period, recent activity, capabilities, attention items, voucher gaps, chart of accounts, VAT treatments)
widgets/ — inline HTML widgets (receipt-matcher, vat-review)
prompts/ — slash-command-style prompts
skills/ — domain-knowledge skill bodies served via gnubok_load_skill
__tests__/ — strictness guards + per-tool coverage