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…

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

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

Soutien

supermathie (Michael Brown) Mars 29, 2026, 3:11 4

De plus, s’agit-il d’une erreur trompeuse que nous pouvons améliorer ?

2 « J'aime »

Sujet		Réponses	Vues
User API keys specification Integrations rest-api , reference	70	35122	Septembre 22, 2025
Allow API use by regular users, not just admins Dev rest-api	7	1296	Avril 29, 2023
Access via Discourse API, key and/or user rejected Dev rest-api	2	850	Décembre 1, 2023
403 error when connecting Zapier to Discourse Support	14	912	Octobre 25, 2020
Get an API key's scopes and user level via the API Dev rest-api	0	597	Novembre 16, 2023

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

Sujets connexes