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 merged 03:0…

[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

Soutien

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
User API keys specification Integrations rest-api , reference	70	35422	Septembre 22, 2025
Allow API use by regular users, not just admins Development rest-api	7	1330	Avril 29, 2023
Access via Discourse API, key and/or user rejected Development rest-api	2	864	Décembre 1, 2023
403 error when connecting Zapier to Discourse Support	14	922	Octobre 25, 2020
Get an API key's scopes and user level via the API Development rest-api	0	609	Novembre 16, 2023

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

Sujets connexes