Claude Desktop OAuth is granted
mcp:read and mcp:write scopes (all Noux MCP OAuth connections use both). Claude can query your organization’s data and call write tools (comments, invitations, notifications, key document spread, mutual action plans) as you — limited by your room permissions in Noux. Reconnect the connector if you connected before this change and need write tools.Before you start
- A Noux account with access to your organization
- Claude Desktop with Connectors enabled (current desktop app)
- Network access to
https://mcp.noux.appandhttps://noux.app
Step 1 — Open Connectors
- Open Claude Desktop.
- Click your profile or settings menu and choose Customize (or Settings).
- Select Connectors in the sidebar.
- Click the + button to add a connector.
Step 2 — Add the Noux connector
Fill in the form:Advanced settings
Expand Advanced settings only if you need them. For the standard Noux setup:- Leave OAuth Client ID empty
- Leave OAuth Client Secret empty
Step 3 — Connect and sign in
- Find Noux in your Connectors list.
- Click Connect.
- Your browser opens the Noux authorization flow:
- Sign in to noux.app if you are not already logged in
- Review the consent screen — it explains what MCP access Claude is requesting
- Click Allow access.
Step 4 — Verify it works
Start a new conversation in Claude Desktop and ask something that uses Noux data, for example:- “Use Noux to call
get_infoand tell me my organization id.” - “List my Noux sales rooms.”
- “Summarize recent activity in my Noux organization.”
What Claude can access
Through OAuth, Claude acts as you in your Noux organization withmcp:read and mcp:write scopes. That includes:
- Rooms, members, visitors, and invitations
- Room conversations and comments
- Notetaker meetings, transcripts, summaries, and coaching
- Organization activity for reporting
- Write tools such as posting comments, sending invitations and update notifications, spreading key documents, and creating or updating mutual action plans — subject to your room permissions
Troubleshooting
For Cursor, automation scripts, or other clients that do not support Connectors OAuth, use a personal Bearer token instead.
Alternative — manual config (legacy)
Older Claude Desktop versions used a JSON config file with a static Bearer token. That approach still works for automation but is not recommended for Claude Desktop now that Connectors and OAuth are available. If you must use manual configuration: macOS:~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Related
- Getting started
- Cursor — uses Bearer tokens, not Connectors
- Tool reference
- MCP overview