afpnews-mcp-server 2.1.0 → 3.0.0-next.0

package/.env.example

@@ -9,4 +9,7 @@ JWT_SECRET=                          # générer avec: openssl rand -base64 32
 MCP_SERVER_URL=https://news-mcp.example.com
 PORT=3000                            # optionnel, défaut: 3000
 MCP_TRANSPORT=http                   # stdio ou http
-MCP_SESSION_TTL=3600000              # optionnel, ms, défaut: 1h
+
+# Callback OAuth des clients IA distants (hors localhost, toujours autorisé).
+# Liste unique, séparée par des virgules — voir README.md pour les valeurs connues.
+MCP_ALLOWED_REDIRECT_URIS=https://claude.ai/api/mcp/auth_callback,https://claude.com/api/mcp/auth_callback

package/CHANGELOG.md

@@ -0,0 +1,114 @@
+# Changelog
+
+All notable changes to this project are documented here. Format loosely follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versioning follows
+[Semantic Versioning](https://semver.org/).
+
+## [3.0.0] — 2026-08-25
+
+### Breaking
+
+- **HTTP transport is now stateless.** The previous session-map model
+  (`mcp-session-id`, `MCP_SESSION_TTL`) is gone — every request now gets a
+  fresh `McpServer` built straight from its own bearer token, so any number
+  of instances can sit behind a plain load balancer with no sticky sessions.
+  Deployments that relied on `MCP_SESSION_TTL` or session affinity need to
+  drop that configuration.
+- Migrated from `@modelcontextprotocol/sdk` (v1) to the split v2 packages
+  (`@modelcontextprotocol/server`, `@modelcontextprotocol/hono`), targeting
+  the 2026-07-28 MCP spec.
+- HTTP framework: **Elysia → Hono**. Framework-specific behavior (error
+  response shapes in particular) changed accordingly.
+- `/oauth/token` now only accepts `application/x-www-form-urlencoded`
+  request bodies (RFC 6749 §4.1.3), not JSON.
+- Access tokens are now bound to this server's own `/mcp` resource via an
+  `aud` claim (RFC 8707); tokens minted by a different deployment are no
+  longer accepted even if it shares the same `JWT_SECRET`.
+- 401 responses on `/mcp` now carry a spec-compliant `WWW-Authenticate`
+  header pointing at the protected-resource metadata document, replacing
+  the previous ad hoc header/body shape.
+
+### Added
+
+- Deployable as a **Cloudflare Worker** (`src/http/worker.ts`, `wrangler.toml`)
+  with no KV/Durable Objects/other bindings — the OAuth authorization code
+  and bearer tokens are all self-contained.
+- `src/http/server.ts` split into `resolveHttpConfig()` / `createHttpApp()` /
+  `startHttpServer()`, so the Hono app itself has no Bun or Node dependency.
+
+### Changed
+
+- The OAuth authorization code is now a self-contained token (same JWE
+  pattern as the access/refresh tokens) instead of server-side state.
+- `node:crypto` dropped in favor of Web Crypto (`crypto.subtle`) for HKDF
+  key derivation and the PKCE challenge check — portable across Bun,
+  browsers, and Workers.
+- Rate limiting (`elysia-rate-limit`) removed; left to the hosting platform
+  (e.g. Cloudflare's own Rate Limiting) rather than a hand-rolled,
+  per-isolate in-process limiter.
+- `/.well-known/oauth-authorization-server` and
+  `/.well-known/oauth-protected-resource/mcp` are now served via the SDK's
+  own metadata helpers instead of hand-written JSON.
+
+### Fixed
+
+- The JWE's registered `exp` claim was silently overwritten by
+  `setExpirationTime()`, so decrypted tokens never carried the real AFP
+  token expiry — moved to a dedicated `texp` claim.
+- A `globalThis.fetch` mock in `get-media-handler.test.ts` was leaking into
+  whichever test file ran next (test-isolation bug).
+
+## [2.2.0] — 2026-08-01
+
+- Snapshot prior to the SDK v2 / Hono / Cloudflare Workers work above.
+
+## [2.0.2] — 2026-06-09
+
+- Fix: `lang` facet examples corrected to `langs` in docs and tests.
+- Improved typing, text truncation, and test infrastructure.
+
+## [2.0.0] — 2026-03-17
+
+- Migrated package manager from pnpm to **Bun**; test runner from Vitest to
+  `bun test`.
+- HTTP transport rewritten on **Elysia** (replacing Express), split into
+  `src/http/` submodules; stdio transport extracted to `src/stdio/server.ts`.
+- OAuth2/OIDC hardening: AFP refresh token stored in a JWE (no credentials
+  persisted server-side), strict `redirect_uri` allowlist, and a round of
+  security-audit fixes.
+- Added `afp_search_media` / `afp_get_media` tools, with base64 image embed
+  for vision models and dedicated media formatting (`format-media.ts`).
+- `product` facet replaced with `class` throughout; added `event` field to
+  the AFP document model.
+- `src/mcp-server.ts` renamed from `server.ts` to avoid a naming collision
+  with `http/server.ts`.
+
+## [1.3.10] — 2026-02-22
+
+- `baseUrl` support (`APICORE_BASE_URL`) added and covered by tests.
+
+## [1.3.7] — 2026-02-20
+
+- `afpshortid` field added; `afp_list_facets` fixes.
+
+## [1.3.4] — 2026-02-17
+
+- Tool definitions' JSON Schemas generated via Zod v4's built-in `toJSONSchema`.
+
+## [1.3.2] and earlier
+
+- Initial tool set (search, get article, similar articles, facets),
+  prompts (daily briefing, comprehensive analysis, factcheck, country news),
+  and the AFP Stories topics resource.
+- HTTP transport added alongside stdio; auth token caching.
+- Package renamed to `afpnews-mcp-server`; pre-converted JSON Schemas
+  exported for cross-instance compatibility.
+- A Notification Center implementation was added and then reverted (the
+  underlying AFP API endpoint wasn't functional).
+
+[3.0.0]: https://github.com/julesbonnard/afpnews-mcp-server/compare/v2.0.2...v3.0.0
+[2.0.2]: https://github.com/julesbonnard/afpnews-mcp-server/compare/v2.0.0...v2.0.2
+[2.0.0]: https://github.com/julesbonnard/afpnews-mcp-server/compare/v1.3.10...v2.0.0
+[1.3.10]: https://github.com/julesbonnard/afpnews-mcp-server/compare/v1.3.7...v1.3.10
+[1.3.7]: https://github.com/julesbonnard/afpnews-mcp-server/compare/v1.3.4...v1.3.7
+[1.3.4]: https://github.com/julesbonnard/afpnews-mcp-server/compare/v1.3.2...v1.3.4

package/CLAUDE.md

@@ -4,7 +4,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Project Overview
 
-MCP (Model Context Protocol) server that exposes AFP news tools for LLM-based editors (Continue, Claude Code, etc.). Supports stdio and HTTP (Streamable HTTP) transports.
+MCP (Model Context Protocol) server that exposes AFP news tools for LLM-based editors (Continue, Claude Code, etc.). Supports stdio and HTTP (stateless Streamable HTTP) transports, targeting the 2026-07-28 MCP spec via the `@modelcontextprotocol/server` v2 SDK.
 
 ## Commands
 
@@ -42,8 +42,9 @@ src/
 │   ├── index.ts          # registerResources() MCP glue
 │   └── topics.ts         # TOPICS inline + resource handler
 ├── http/
-│   ├── server.ts         # Elysia HTTP server + OAuth2 PKCE auth
-│   ├── tokens.ts         # JWT helpers (encrypt/decrypt AFP tokens)
+│   ├── server.ts         # resolveHttpConfig() + createHttpApp() (Hono, platform-agnostic) + startHttpServer() (Bun)
+│   ├── worker.ts         # Cloudflare Worker entry point — same createHttpApp(), config from the `env` binding
+│   ├── tokens.ts         # JWT helpers (encrypt/decrypt AFP tokens, self-contained auth code)
 │   └── login-page.ts     # OAuth login page + redirect URI helpers
 ├── stdio/
 │   └── server.ts         # stdio transport entry
@@ -54,9 +55,9 @@ src/
 ```
 
 1. Creates an `ApiCore` client from `afpnews-api` using `APICORE_API_KEY`
-2. Registers MCP tools via `@modelcontextprotocol/sdk`: `afp_search_articles`, `afp_get_article`, `afp_find_similar`, `afp_list_facets`, `afp_search_media`, `afp_get_media`
+2. Registers MCP tools via `@modelcontextprotocol/server`: `afp_search_articles`, `afp_get_article`, `afp_find_similar`, `afp_list_facets`, `afp_search_media`, `afp_get_media`
 3. Authenticates with username/password on first call, then reuses or refreshes the token for subsequent queries
-4. Supports two transports: stdio (default) and HTTP (`MCP_TRANSPORT=http`, uses Elysia + Streamable HTTP with OAuth2 PKCE per-session)
+4. Supports two transports: stdio (default) and HTTP (`MCP_TRANSPORT=http`, uses Hono + `createMcpHandler()` — a fresh `McpServer` per request, no session store or other server-side state, OAuth2 PKCE per-request bearer token). HTTP has two entry points sharing the same `createHttpApp()`: `startHttpServer()` (Bun, `Bun.serve`) and `worker.ts` (Cloudflare Worker, `export default { fetch }`) — see "Cloudflare Workers" in README.md for deployment.
 
 ### Definitions-First Pattern
 
@@ -87,9 +88,10 @@ Required:
 - `MCP_TRANSPORT=http`
 
 Optional:
-- `PORT` — HTTP server port (default: 3000)
-- `MCP_SESSION_TTL` — Session duration in milliseconds (default: 3600000 = 1h)
-- `MCP_ALLOWED_REDIRECT_URIS` — Comma-separated list of allowed OAuth redirect URIs
+- `PORT` — HTTP server port (default: 3000; ignored on Cloudflare Workers, which has no port to bind)
+- `MCP_ALLOWED_REDIRECT_URIS` — Comma-separated list of allowed OAuth redirect URIs. The single place to allowlist AI clients with a fixed callback URL (Claude, ChatGPT, Mistral...) — `localhost`/`127.0.0.1` is always allowed separately, no entry needed for local clients. See README.md for known values.
+
+On Workers, these are read from the `env` binding (`wrangler.toml` `[vars]` + `wrangler secret put`) instead of `process.env`, which doesn't exist there — see `src/http/worker.ts` and README.md.
 
 ## Key Details
 

package/README.md

@@ -50,7 +50,10 @@ For local MCP clients like Claude Code or Claude Desktop:
 
 ### HTTP transport
 
-For remote or multi-user deployments. Users authenticate via OAuth2 PKCE using their AFP credentials.
+For remote or multi-user deployments. Stateless: each request is served by a fresh MCP server
+instance built from that request's own bearer token, so any number of instances can sit behind
+a plain round-robin load balancer with no sticky sessions or shared store. Users authenticate via
+OAuth2 PKCE using their AFP credentials.
 
 Required environment variables for HTTP mode:
 
@@ -64,8 +67,17 @@ PORT=3000
 ```
 
 Optional:
-- `MCP_SESSION_TTL` — session duration in milliseconds (default: 3600000 = 1h)
-- `MCP_ALLOWED_REDIRECT_URIS` — comma-separated list of allowed OAuth redirect URIs
+- `MCP_ALLOWED_REDIRECT_URIS` — comma-separated list of allowed OAuth redirect URIs.
+  `localhost`/`127.0.0.1` (any port) is always allowed regardless of this list —
+  it covers any client that runs a local OAuth callback server (Claude Code,
+  MCP Inspector, most IDEs). This var is the single place to allowlist clients
+  with a fixed, non-localhost callback URL. Known ones:
+  - Claude: `https://claude.ai/api/mcp/auth_callback`, `https://claude.com/api/mcp/auth_callback`
+  - ChatGPT: `https://chatgpt.com/connector_platform_oauth_redirect`, `https://chatgpt.com/oauth/callback`, `https://chat.openai.com/oauth/callback`
+  - Mistral (Le Chat): `https://callback.mistral.ai/v1/integrations_auth/oauth2_callback`
+
+  Add others as you connect new clients — the exact `redirect_uri` shows up in
+  the failed `/oauth/authorize` request when a client isn't allowlisted yet.
 
 ```bash
 bun src/index.ts
@@ -87,6 +99,30 @@ docker run \
   afpnews-mcp
 ```
 
+### Cloudflare Workers
+
+The HTTP transport is built as a plain [Hono](https://hono.dev) app with no server-side state
+(the OAuth authorization code and the bearer tokens are all self-contained), so it also runs as a
+Cloudflare Worker via `src/http/worker.ts` — no KV, Durable Objects, or other bindings needed.
+
+```bash
+bunx wrangler login
+bunx wrangler secret put APICORE_API_KEY
+bunx wrangler secret put JWT_SECRET
+```
+
+Edit `wrangler.toml`'s `[vars]` (`APICORE_BASE_URL`, `MCP_SERVER_URL` — the latter must match your
+actual `*.workers.dev` subdomain or custom domain), then:
+
+```bash
+bun run dev:worker      # local dev server via workerd (bunx wrangler dev)
+bun run deploy:worker   # bunx wrangler deploy
+```
+
+Rate limiting isn't implemented in-process (it would be per-isolate and largely pointless on the
+edge) — use [Cloudflare's own Rate Limiting](https://developers.cloudflare.com/waf/rate-limiting-rules/)
+in front of the Worker instead.
+
 ### As a library (without MCP server dependency)
 
 You can import pure definitions (tools, prompts, resources) and wire them into your own runtime: