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-18T12:09:13.703Z] INFO Starting Discourse MCP v0.2.6 [2026-03-18T12:09:16.679Z] ERROR HTTP 403 Forbidden for GET ``https://qna.tax/about.json:`` {“errors”:[“You are not permitted to view the requested resource. The API username or key is invalid.”],“error_type”:“invalid_access”} [2026-03-18T12:09:16.679Z] ERROR Failed to validate --site ``https://qna.tax``: HTTP 403 Forbidden There is no option anywhere to grant or revoke read access to “about” on granular permission. [image] Current workaround: Switching to a global API key (not scoped) resolves the 403 — but that’s not viable for any production setup where least-privilege access matters. Either about.json should be accessible to any valid API key regardless of scope (since it’s public site metadata), or the granular permissions UI should include an explicit option to whitelist it.

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

[image] 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.

Utilisateur API avec accès granulaire ne peut pas lire about.json | Discourse MCP

Assistance produit

supermathie (Michael Brown) Avril 21, 2026, 3:06 9

J’ai fusionné la modification. Une fois que l’état tests-passed sera atteint, vous pourrez reconstruire et récupérer la version mise à jour ; tout devrait alors fonctionner.

Sujet		Réponses	Vues
Request ESR backport: Allow granular API keys access to about.json Development mcp	2	173	Juillet 28, 2026
Confirming API Access to Authoring Limit Site Settings Development rest-api	4	292	Juillet 25, 2026
User API keys specification Integrations rest-api , reference	69	38677	Septembre 22, 2025
Allow API use by regular users, not just admins Development rest-api	6	1665	Février 14, 2023
Feature request: Allow safe API access to site settings without an admin-level key Feature rest-api	9	349	Juillet 27, 2026

Utilisateur API avec accès granulaire ne peut pas lire about.json | Discourse MCP

Sujets connexes