Noux MCP is read-only. Claude can query your organization’s rooms, meetings, and conversations as you, but cannot create or modify data.
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:| Field | Value |
|---|---|
| Name | Noux |
| Remote MCP Server URL | https://mcp.noux.app/mcp |
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 that the client requests read-only MCP access to your organization
- 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 with read-only scope (mcp:read). That includes:
- Rooms, members, visitors, and invitations
- Room conversations and comments
- Notetaker meetings, transcripts, summaries, and coaching
- Organization activity for reporting
Troubleshooting
| Issue | What to try |
|---|---|
| Connector fails to add | Confirm URL is https://mcp.noux.app/mcp with no trailing spaces |
| Browser opens but login fails | Use the same email you use for Noux; contact your org admin if access is blocked |
| Consent page does not appear | Complete sign-in at noux.app first, then click Connect again in Claude |
| ”Unauthorized” after connecting | Click Connect again to refresh OAuth tokens; deny and re-approve if needed |
| Tools not showing in chat | Restart Claude Desktop; ensure the Noux connector shows as connected |
| Wrong organization data | OAuth is tied to the Noux account you signed in with — sign out and reconnect with the correct account |
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