← All integrations

Connect Noded to Microsoft Copilot Studio

Add the Noded MCP server as a tool in a Copilot Studio agent, then publish that agent to Microsoft 365 Copilot. Copilot can then find your customer context - people, accounts, emails, meetings, notes, tasks, and records - and propose drafts and actions that you approve or dismiss before anything happens.

TL;DR: In Copilot Studio open your agent’s Tools page → Add a tool → New tool → Model Context Protocol, enter https://app.getnoded.ai/api/mcp/apps, choose OAuth 2.0 → Dynamic discovery, and sign in to Noded. No client ID or secret to enter - Copilot Studio registers itself with Noded’s sign-in service automatically. Publish the agent to Microsoft 365 Copilot. Reads are read-only. Every write (an email, a message, a note, a CRM record, a workflow run) arrives as a recommendation that you approve or dismiss.

What you need

  • A Noded account with data connected. Copilot can only find what Noded has synced. Connect at least one source (Gmail, Outlook, Slack, Teams, a calendar, a call recorder, or a CRM) in the Noded app first.
  • No client ID or secret. Copilot Studio supports OAuth 2.0 dynamic client registration with discovery, and Noded’s sign-in service supports it too, so the wizard registers itself and asks you to sign in - the same as Claude and ChatGPT. If your tenant policy requires a pre-registered client, request an OAuth client and use the Manual option instead (see the note under step 4).
  • Access to Copilot Studio. Copilot Studio is included with Microsoft 365, but a tenant admin may need to deploy the Copilot Studio app in the Microsoft 365 admin center and enable generative AI features in the Power Platform admin center. See Microsoft’s Copilot Studio requirements.
  • The server URL. https://app.getnoded.ai/api/mcp/apps - enter it exactly, including the path.

You do not need a Microsoft marketplace listing, a Partner Center submission, or the Microsoft 365 Agents Toolkit for this path. The Noded server is added to an agent you own, inside your own tenant.

Who can set this up?

RoleWhat they can do
Anyone who can open Copilot Studio (a maker)Add Noded as an MCP tool to an agent they own, sign in, and use it in the Test pane. No credentials from Noded and no admin involved, unless one of the two rows below applies.
Microsoft 365 or Power Platform adminMay need to deploy the Copilot Studio app and enable generative AI features for the environment before makers can use it; can block the connector with a data loss prevention (DLP) policy; and may need to approve the agent under Integrated apps before it can be shared with the organization in Microsoft 365 Copilot.
Everyone else in Microsoft 365 CopilotUses the published agent. They cannot add MCP tools themselves; each person signs in to Noded the first time the agent calls it, so everyone sees only their own Noded data.

In short: a CSM with Copilot Studio access can set this up alone for their own use; sharing it with the whole company is where an admin comes in.

Using another assistant? See the guides for Claude, ChatGPT, Gemini, and Slackbot.

Add Noded to a Copilot Studio agent

1️⃣ Open or create an agent. Go to copilotstudio.microsoft.com and sign in with your work account. Open an existing agent, or select Create → New agent, give it a name, and select Create.

2️⃣ Start the MCP wizard. On the agent, open the Tools tab. Select Add a tool → New tool → Model Context Protocol.

3️⃣ Describe the server. Fill in the basic details:

FieldValue
Server nameNoded
Server descriptionCustomer context from Noded: people, accounts, emails, meetings, notes, tasks, and CRM or support records, plus draft emails, messages, and records for review. The orchestrator uses this text to decide when to call Noded, so keep it accurate.
Server URLhttps://app.getnoded.ai/api/mcp/apps
AuthenticationOAuth 2.0, type Dynamic discovery (the default)

4️⃣ Create the server. Leave Dynamic discovery selected and select Create. Copilot Studio reads Noded’s OAuth metadata from the server URL, registers itself as a client, and creates a custom connector for the tool. There are no URLs, scopes, or secrets to paste, and no callback URL to send us - registration carries Copilot’s callback with it.

Prefer a pre-registered client? Choose Manual instead and enter the client ID and secret Noded issued you, with authorization URL https://app.getnoded.ai/api/auth/oauth2/authorize, token and refresh URL https://app.getnoded.ai/api/auth/oauth2/token, and scopes openid profile email offline_access. Copilot Studio then shows a callback URL (it starts with https://global.consent.azure-apim.net/) - send it to us with your request and we add it to the client.

5️⃣ Connect. On Add tool, open the Connection menu and select Create new connection, then Create. A Noded sign-in window opens. Use the same email address as your Noded account, then approve the requested access. The consent screen lists read access to your customer context and the ability to create recommendations for you to review. The connection shows a green tick when it is ready.

6️⃣ Add to agent. Select Add. The Noded tool appears on the agent’s Tools page, switched on.

7️⃣ Test in Copilot Studio. In the Test pane, ask: “What can Noded do?” The agent calls Noded and lists the built-in actions plus the searches, workflows, and record types installed for your account. Then try “When did we last talk to Acme, and is anyone waiting on a reply from us?”

Publish the agent to Microsoft 365 Copilot

1️⃣ Add the channel. Open the agent’s Channels tab, select Teams and Microsoft 365 Copilot, and turn on Make agent available in Microsoft 365 Copilot. Follow the prompts to add the channel.

2️⃣ Publish. Select Publish at the top right of the agent. Copilot Studio validates the agent and makes it available in the channels you selected.

3️⃣ Find it in Copilot. Open Microsoft 365 Copilot Chat. The agent appears under Agents in the left sidebar. Each colleague signs in to Noded the first time the agent calls it, so everyone sees only their own Noded data.

To share the agent beyond yourself, an admin may need to approve it for the organization in the Microsoft 365 admin center under Integrated apps. Microsoft’s guide to publishing an agent to Microsoft 365 Copilot and Teams has the current steps.

What Copilot can do with Noded

Noded exposes one server with a small set of capability groups. You never need the tool names; describe what you want and the agent picks the right one.

GroupWhat it doesExample prompt
Find people and accountsResolves a name or company to the right contact or account, lists related people (buying committee, who else is involved), and reads your saved folders such as My Accounts.“Who else at Acme has been on our calls?”
Read activityEmails, chat messages, meetings and transcriptions, notes, tasks, and saved CRM or support records - filtered by person, account, date, direction, or status. Semantic search finds themes when exact filters are not enough.“What was decided on the last two Acme calls?”
Check engagementPer-account activity across every channel in one call, and unanswered emails - who is waiting on you, and who has gone quiet.“Which of my accounts have gone quiet this month?”
Search connected appsRead-only live lookups in the apps you have connected (Salesforce, HubSpot, Zendesk, Jira, Linear, and others) using the searches installed for your account.“Find open Zendesk tickets for Acme.”
Draft and actDraft an email, a Teams or Slack message, or a note; create a record in a connected system (a Jira issue, a Salesforce case, a HubSpot record); or run one of your installed workflows. Each one arrives as a recommendation to review.“Draft a follow-up to Jane at Acme about next steps.”
DatesHelpers for the current time, relative dates, and date arithmetic so questions such as “in the last 10 days” resolve correctly.“How many days until the Acme renewal?”

The exact list of searches, workflows, and record types is specific to your account. It depends on which apps you have connected in Noded and which queries and functions your team has installed. Ask “What can Noded do?” at any time to see the current list.

Copilot Studio agents show Noded results as text. The interactive result cards that Noded renders in Claude and ChatGPT are not shown in Copilot Studio agents. If you want those cards inside Microsoft 365 Copilot, that is a different build (a declarative agent made with the Microsoft 365 Agents Toolkit) - ask us and we will help.

How the review step works

Noded separates reading from writing. All the read tools are read-only. Every write goes through a recommendation:

1️⃣ Copilot proposes. When you ask for an email, a message, a note, a record, or a workflow run, the agent composes the proposal and asks Noded to create a recommendation. Nothing is sent, saved, created, or run at this point.

2️⃣ You review it. The agent reports the recommendation in the chat: the recipients, the subject and body, the record fields, or the workflow inputs. The same recommendation appears in the Noded app, where you can edit the text before you decide.

3️⃣ Approve or dismiss. Approve accepts the recommendation with your edits, and Noded carries it out through the connected system. Dismiss discards it. If Noded cannot create a recommendation, the agent tells you so instead of pretending the action happened.

Permissions and data handling

  • The connection runs as you. Copilot sees only what your Noded user can see. Tenant boundaries and sharing permissions are the same as in the Noded app. Every colleague who uses the agent signs in to Noded separately.
  • Sign-in is OAuth 2.0 authorization code. Copilot Studio never holds your Noded password. The token is scoped to reading your customer context and creating recommendations. With dynamic discovery, Copilot Studio holds the client registration it created; there is no shared secret for you to store. If you used the Manual option, treat the client secret like a password and share it only with the maker who sets up the tool.
  • Disconnect at any time. Remove the Noded tool from the agent, or delete the connection in Power Apps under Connections. Access ends for that connection immediately.
  • Data policies apply. MCP servers in Copilot Studio run through Power Platform connectors, so your tenant’s data loss prevention (DLP) policy governs the Noded tool the same way it governs any connector.
  • Nothing new is stored in Copilot by Noded. Query results are returned to the chat you are in and are governed by your Microsoft 365 data policies.

Troubleshooting

  • The sign-in window shows an error about a callback or redirect URL. This only happens with the Manual option: the callback URL Copilot Studio showed you is not yet on your client. Send it to us, or check that you copied it exactly. With Dynamic discovery there is nothing to register.
  • Sign-in succeeds but the tool returns “Unauthorized”. Open Manage your connections from the test pane; if the connection shows Stale, create a new one and retry. Also check that you signed in with the same email address as your Noded account.
  • The MCP wizard or Copilot Studio never loads. Try a private browser window (this disables ad blockers and extensions), and ask your admin whether the environment has generative AI features enabled and whether Power Platform endpoints are reachable from your network.
  • The tool is greyed out or blocked. A Power Platform DLP policy is blocking the connector. Your Power Platform admin can move it to the allowed group.
  • Copilot finds nothing for an account you know is active. Check that the source (email, calendar, Teams, Slack, call recorder, CRM) is connected in Noded and has finished its first sync.
  • The agent answers from general knowledge instead of Noded. Make the server description in step 3 more specific, or say “use Noded” in the prompt.

FAQ

Do I need an admin to set this up?

Not to try it: anyone with Copilot Studio access can add Noded to an agent they own and use it in the Test pane. An admin may be needed to enable Copilot Studio and generative AI features, to allow the connector under a DLP policy, and to approve the agent for sharing with the organization in Microsoft 365 Copilot. See who can set this up.

Do I need a client ID and client secret from Noded?

No. Choose Dynamic discovery in the wizard and Copilot Studio registers itself with Noded’s sign-in service automatically, the same way Claude and ChatGPT do. The sign-in itself is the standard OAuth 2.0 authorization code flow. The Manual option still works if your tenant requires a pre-registered client - request one and we will issue it.

Can Copilot send an email or create a record through Noded without asking me?

No. Every write becomes a recommendation. Nothing is sent, saved, created, or run until you approve it.

Which URL do I enter?

https://app.getnoded.ai/api/mcp/apps, entered exactly, including the /api/mcp/apps path.

Do I need to publish a Microsoft app store listing?

No. You add the Noded server to an agent you own and publish that agent inside your own Microsoft 365 tenant. No marketplace listing or Partner Center submission is involved.

Does the same server work with Claude, ChatGPT, and Gemini?

Yes. The same server URL is used for Claude, ChatGPT, and Gemini. See our guide to MCP for customer teams for the wider picture.

Get started

Make your customer data
the best in the business.

For your team, your agents, and every LLM you use. First value in a coffee break - no data cleanup required.

Get started ↗︎ Book a demo

Complex environment? We’ll run the project with you →