We’ve been setting up the Discourse MCP server to connect our Discourse instance to Claude Desktop via config files. When using a single-use API key with granular access controls, the MCP server throws a 403 Forbidden error because it can’t read about.json. Snippet from the Console Logs [2026-03-1…

it seems reasonable to include access to about.json, I’ve opened a PR and will run this by the team DEV: allow granular api keys access to about.json (#38948) main ← dev-about-api-scope opened 01:5…

[画像] aangi: The API username or key is invalid Also, is this a misleading error we can improve?

Hi Michael, it does seem like a misleading error. However, because we cannot change the scope of the user once its been created, it is possible that in case of granular access, the API username is being rendered invalid because there is no about.json file.

APIユーザーがgranular accessでabout.jsonを読み込めない | Discourse MCP

サポート

awesomerobot (Kris) 2026 年 3 月 28 日午後 2:00 3

about.json へのアクセスを含めることは妥当なようです。PR を作成し、チームに確認いたします。

「いいね！」 2

トピック		返信	表示
User API keys specification Integrations rest-api , reference	70	35122	2025 年 9 月 22 日
Allow API use by regular users, not just admins Dev rest-api	7	1296	2023 年 4 月 29 日
Access via Discourse API, key and/or user rejected Dev rest-api	2	850	2023 年 12 月 1 日
403 error when connecting Zapier to Discourse Support	14	912	2020 年 10 月 25 日
Get an API key's scopes and user level via the API Dev rest-api	0	597	2023 年 11 月 16 日

APIユーザーがgranular accessでabout.jsonを読み込めない | Discourse MCP

関連トピック