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) 3월 28, 2026, 2:00오후 3

about.json에 대한 접근 권한을 포함하는 것이 합리적이라고 생각됩니다. PR을 열었고, 팀과 이 문제를 논의할 예정입니다.

글		댓글	조회수
Request ESR backport: Allow granular API keys access to about.json Development mcp	2	128	7월 28, 2026
Confirming API Access to Authoring Limit Site Settings Development rest-api	4	188	7월 25, 2026
User API keys specification Integrations rest-api , reference	69	37383	9월 22, 2025
Allow API use by regular users, not just admins Development rest-api	6	1510	2월 14, 2023
Feature request: Allow safe API access to site settings without an admin-level key Feature rest-api	9	265	7월 27, 2026

세부 권한이 있는 API 사용자는 about.json을 읽을 수 없습니다 | Discourse MCP

Related topics