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…

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

El usuario de la API con acceso granular no puede leer sobre.json | Discourse MCP

Soporte

awesomerobot (Kris) 28 Marzo, 2026 14:00 3

parece razonable incluir el acceso a about.json, he abierto una PR y lo consultaré con el equipo

2 Me gusta

Tema		Respuestas	Vistas
User API keys specification Integrations rest-api , reference	70	35122	22 Septiembre 2025
Allow API use by regular users, not just admins Dev rest-api	7	1296	29 Abril 2023
Access via Discourse API, key and/or user rejected Dev rest-api	2	850	1 Diciembre 2023
403 error when connecting Zapier to Discourse Support	14	912	25 Octubre 2020
Get an API key's scopes and user level via the API Dev rest-api	0	597	16 Noviembre 2023

El usuario de la API con acceso granular no puede leer sobre.json | Discourse MCP

Temas relacionados