Branch: refs/heads/discourse-api-key Home: https://github.com/xwiki/xwiki-dev-llm Commit: 97a2fb87427b422979d8fd5ee5158dd2713855f7 https://github.com/xwiki/xwiki-dev-llm/commit/97a2fb87427b422979d8fd5ee5158d... Author: Vincent Massol <[email protected]> Date: 2026-08-23 (Sun, 23 Aug 2026) Changed paths: M .claude-plugin/marketplace.json M CLAUDE.md M README.md M kimi.plugin.json M opencode.jsonc M xwiki/.claude-plugin/plugin.json M xwiki/.mcp.json M xwiki/okf/servers/index.md A xwiki/scripts/start-discourse-mcp.mjs Log Message: ----------- [Misc] Allow the discourse MCP server to post on the forum * Read a forum credential from the environment: DISCOURSE_API_KEY + DISCOURSE_API_USERNAME (admin key), or DISCOURSE_USER_API_KEY + DISCOURSE_USER_API_CLIENT_ID (user key, which any account can hold). With none set, the server stays anonymous and read-only exactly as before. * Start the server through a new launcher, xwiki/scripts/start-discourse-mcp.mjs, wired into all three host manifests. A wrapper is needed because the write flags must be added only when a credential is actually present, which a static MCP manifest cannot express. * Pass the credential in a temporary 0600 profile file instead of on the command line, so it never appears in the machine's process list. * Drop a credential the forum refuses (401/403) and start read-only instead: the server authenticates its own start-up call to /about.json, so a stale key otherwise makes it register no tools at all and every forum tool silently disappears. A network or server-side error keeps the credential. * Document the variables and how to obtain each kind of key in the README, and record in the OKF that a missing post tool means "no credential set" rather than "posting unavailable". Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications