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

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

Usuário da API com acesso granular não consegue ler sobre.json | Discourse MCP

Suporte

supermathie (Michael Brown) 21 Abril , 2026 15:06 9

Já fundi a alteração, então assim que ela atingir o status de testes aprovados, você pode reconstruir e puxar a versão atualizada, e tudo deverá funcionar.

Tópico		Respostas	Vistas
Request ESR backport: Allow granular API keys access to about.json Development mcp	2	78	28 Julho , 2026
Confirming API Access to Authoring Limit Site Settings Development rest-api	4	138	25 Julho , 2026
User API keys specification Integrations rest-api , reference	69	36812	22 Setembro , 2025
Allow API use by regular users, not just admins Development rest-api	6	1445	14 Fevereiro , 2023
Access via Discourse API, key and/or user rejected Development rest-api	2	908	1 Dezembro , 2023

Usuário da API com acesso granular não consegue ler sobre.json | Discourse MCP

Related topics