The Noux MCP server lets AI clients such as Cursor and Claude Desktop query your organization’s Noux data using the Model Context Protocol.
MCP access is read-only in the current version. Tokens are personal — each token acts as you within your organization.
What you can do
Connect an MCP client to:
- List rooms, members, and visitors
- Read room conversations, comments, and invitations
- Query mutual action plans with tasks, assignees, due dates, and progress
- Access notetaker meetings, transcripts, summaries, and coaching
- Pull activity data for reporting
MCP vs REST API
| Noux MCP | REST API |
|---|
| Purpose | AI assistants querying your data | Application integrations and automation |
| Auth | Personal MCP token | Organization API key |
| Access | Read-only | Create and update resources |
| Docs | MCP tools | API reference |
| Setup | Integrations → MCP | Integrations → API |
Transport and endpoint
Noux MCP uses Streamable HTTP at:
The same URL is shown in the Noux app under Integrations → MCP.
Claude Desktop authenticates via OAuth when you connect the custom connector — no manual header.
Cursor and automation send a Bearer token on every request:
Authorization: Bearer <your-mcp-token>
Capabilities
Call the get_info tool after connecting to confirm your organization id, user id, and that read_only is in the capabilities list. All tools are annotated with readOnlyHint: true for clients that respect MCP tool hints.
Authentication
| Client | How to authenticate |
|---|
| Claude Desktop | OAuth — add a custom connector and sign in to Noux when prompted |
| Cursor, scripts | Personal Bearer token from Integrations → MCP |
https://mcp.noux.app/mcp
Next steps
- Getting started — tokens (for Cursor) or OAuth overview (for Claude)
- Claude Desktop or Cursor — client-specific setup
- Tool reference — all available tools, inputs, and pagination