> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nouxdigital.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Microsoft Copilot Studio

> Connect a Copilot Studio agent to Noux MCP using OAuth dynamic discovery.

Microsoft Copilot Studio connects to Noux through **Model Context Protocol** tools on your agent. You sign in with your Noux account; no manual token copying required when you use OAuth.

<Note>
  Copilot Studio OAuth is granted **`mcp:read` and `mcp:write`** scopes (all Noux MCP OAuth connections use both). Your agent 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.
</Note>

## Before you start

* A **Noux account** with access to your organization
* **Microsoft Copilot Studio** access in a Power Platform environment
* **Generative orchestration** enabled on your agent ([Microsoft docs](https://learn.microsoft.com/en-us/microsoft-copilot-studio/advanced-generative-actions))
* Network access to `https://mcp.noux.app` and `https://noux.app`

You do **not** need to create a personal Bearer token for OAuth — Noux registers Copilot Studio automatically using OAuth 2.1 dynamic client registration.

***

## Step 1 — Add the Noux MCP tool

1. Open your agent in **Copilot Studio**.
2. Go to **Tools**.
3. Select **Add a tool** → **New tool** → **Model Context Protocol**.
4. Fill in the form:

| Field                  | Value                                           |
| ---------------------- | ----------------------------------------------- |
| **Server name**        | `Noux`                                          |
| **Server description** | e.g. "Noux sales rooms, meetings, and activity" |
| **Server URL**         | `https://mcp.noux.app/mcp`                      |
| **Authentication**     | **OAuth 2.0**                                   |

### OAuth configuration (recommended)

Under **OAuth 2.0**, choose **Dynamic discovery**. Copilot Studio reads Noux OAuth metadata from the MCP server and registers itself automatically. You do not need to paste Client ID, Client secret, or endpoint URLs.

<Warning>
  Only add MCP servers from developers you trust. The URL must be exactly `https://mcp.noux.app/mcp` — including the `/mcp` path.
</Warning>

Select **Create**, then **Next**.

### Alternative — Dynamic (manual endpoints)

If Dynamic discovery is unavailable in your environment, choose **Dynamic** and enter:

| Field                  | Value                                  |
| ---------------------- | -------------------------------------- |
| **Authorization URL**  | `https://noux.app/api/oauth/authorize` |
| **Token URL template** | `https://noux.app/api/oauth/token`     |

Copilot Studio may show a **callback URL** after you create the tool. Noux already allows Power Platform redirect URIs under `https://global.consent.azure-apim.net/redirect/...` — you do not need to contact Noux support for each connector.

Select **Next** when the tool is created.

***

## Step 2 — Create a connection

1. On **Add tool**, select **Create a new connection** (or reuse an existing Noux connection).
2. Sign in to **Noux** when prompted:
   * Complete login at [noux.app](https://noux.app) if needed
   * Review the consent screen
3. Click **Allow access**.
4. Select **Add to agent**.

Copilot Studio receives an OAuth access token scoped to your user and organization.

<Note>
  **Published agents:** end-user OAuth for custom MCP servers is still evolving in Copilot Studio. If published users see an empty connection picker, use a **maker-managed connection** (single shared connection for the agent) until per-user OAuth is supported in your tenant.
</Note>

***

## Step 3 — Verify it works

Test your agent with prompts that use 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."

The agent should invoke Noux MCP tools (see the [tool reference](/mcp/tools)). If tools are not available, recreate the connection or republish the agent after fixing authentication.

***

## What Copilot Studio can access

Through OAuth, your agent 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 Copilot Studio, use a [personal Bearer token](/mcp/getting-started) in Cursor or scripts, or the [REST API](/api/overview) with an organization API key.

***

## Alternative — API key authentication

Copilot Studio can connect with **API key** auth and a personal Bearer token instead of OAuth. This works for quick tests but is **not recommended** for regular use — tokens must be copied manually and rotated by you.

1. Create a token under [Integrations → MCP](https://noux.app/integrations/mcp).
2. When adding the MCP tool, set **Authentication** to **API key**.
3. Choose **Header** and name the header `Authorization`.
4. Use server URL `https://mcp.noux.app/mcp` and value `Bearer <your-token>`.

Prefer **OAuth 2.0 → Dynamic discovery** for production and team use.

***

## Troubleshooting

| Issue                           | What to try                                                                                  |
| ------------------------------- | -------------------------------------------------------------------------------------------- |
| Tool creation fails             | Confirm URL is `https://mcp.noux.app/mcp` with no trailing spaces                            |
| OAuth redirect error            | Use **Dynamic discovery** or **Dynamic** (not Manual unless you manage credentials yourself) |
| 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    | Sign in at noux.app first, then recreate the connection                                      |
| "Unauthorized" after connecting | Create a new connection and re-approve Noux access                                           |
| Tools not invoked in chat       | Enable generative orchestration; check the tool description is clear; test in the Test pane  |
| Published users cannot connect  | Use a maker-managed connection; custom MCP end-user OAuth is limited in preview              |
| Wrong organization data         | OAuth is tied to the Noux account you signed in with — reconnect with the correct account    |

***

## Related

* [Getting started](/mcp/getting-started)
* [Claude Desktop](/mcp/clients/claude-desktop)
* [ChatGPT](/mcp/clients/chatgpt)
* [Cursor](/mcp/clients/cursor) — uses Bearer tokens, not OAuth
* [Tool reference](/mcp/tools)
* [MCP overview](/mcp/overview)