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 https://github.com/discourse/discourse/pull/38948

[图片] 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.

Hi @awesomerobot @supermathie any update on this?

I’ve merged the change, so once it hits tests-passed you can rebuild and pull in the updated version and everything should work.

API 用户拥有精细权限却无法读取 about.json | Discourse MCP

支持

awesomerobot (Kris) 2026 年3 月 28 日 14:00 3

看起来包含对 about.json 的访问权限是合理的，我已经提交了一个 PR，并将与团队讨论此事。

话题		回复	浏览量
Request ESR backport: Allow granular API keys access to about.json Development mcp	2	121	2026 年7 月 28 日
Confirming API Access to Authoring Limit Site Settings Development rest-api	4	170	2026 年7 月 25 日
User API keys specification Integrations rest-api , reference	69	37178	2025 年9 月 22 日
Allow API use by regular users, not just admins Development rest-api	6	1482	2023 年2 月 14 日
Feature request: Allow safe API access to site settings without an admin-level key Feature rest-api	9	234	2026 年7 月 27 日

API 用户拥有精细权限却无法读取 about.json | Discourse MCP

相关话题