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

[afbeelding] 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?

API user with granular access cannot read about.json | Discourse MCP

Ondersteuning

supermathie (Michael Brown) 21 april 2026 om 15:06 9

I’ve merged the change, so once it hits tests-passed you can rebuild and pull in the updated version and everything should work.

Topic		Antwoorden	Weergaven
Request ESR backport: Allow granular API keys access to about.json Development mcp	2	148	28 juli 2026
Confirming API Access to Authoring Limit Site Settings Development rest-api	4	227	25 juli 2026
User API keys specification Integrations rest-api , reference	69	37613	22 september 2025
Allow API use by regular users, not just admins Development rest-api	6	1530	14 februari 2023
Feature request: Allow safe API access to site settings without an admin-level key Feature rest-api	9	290	27 juli 2026

API user with granular access cannot read about.json | Discourse MCP

Gerelateerde topics