Skip to main content
Claude Desktop connects to Noux through Connectors — Anthropic’s built-in UI for remote MCP servers. You sign in with your Noux account; no manual token copying required.
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.app and https://noux.app
You do not need to create a personal Bearer token for Claude Desktop — OAuth handles authentication.

Step 1 — Open Connectors

  1. Open Claude Desktop.
  2. Click your profile or settings menu and choose Customize (or Settings).
  3. Select Connectors in the sidebar.
  4. Click the + button to add a connector.
Choose Add custom connector (may show a BETA badge).

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
Noux registers Claude automatically using OAuth 2.1 dynamic client registration. You do not need to paste credentials from the Noux app.
Only add connectors from developers you trust. The URL must be exactly https://mcp.noux.app/mcp — including the /mcp path.
Click Add.

Step 3 — Connect and sign in

  1. Find Noux in your Connectors list.
  2. Click Connect.
  3. 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
  4. Click Allow access.
Claude Desktop receives an OAuth access token scoped to your user and organization. The connector should show as connected.

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_info and tell me my organization id.”
  • “List my Noux sales rooms.”
  • “Summarize recent activity in my Noux organization.”
Claude should invoke Noux MCP tools (see the tool reference). If tools are not available, disconnect and reconnect the connector, or restart Claude Desktop.

What Claude can access

Through OAuth, Claude acts as you in your Noux organization with mcp: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
For automation without Claude, use a personal Bearer token in Cursor or scripts, or the REST API with an organization API key.

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.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Create the token under Integrations → MCP. Restart Claude Desktop after saving.