TL;DR: Request an OAuth client ID and secret from Noded, then 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 → Manual, and paste the values below. 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.
- An OAuth client ID and client secret from Noded. Copilot Studio’s automatic (dynamic) registration does not complete against Noded’s sign-in service, so we issue credentials for your workspace. Email hello@getnoded.ai with the subject OAuth client for Copilot Studio and the email address of your Noded workspace. We reply with a client ID and a client secret.
- 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.
Using another assistant? See the guides for Claude, ChatGPT, and Gemini.
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:
| Field | Value |
|---|---|
| Server name | Noded |
| Server description | Customer 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 URL | https://app.getnoded.ai/api/mcp/apps |
| Authentication | OAuth 2.0, type Manual |
4️⃣ Enter the OAuth settings. Under Manual, paste these values. The client ID and client secret are the ones Noded sent you.
| Field | Value |
|---|---|
| Client ID | From Noded |
| Client secret | From Noded |
| Authorization URL | https://auth.getnoded.ai/authorize?audience=https://api.noded.so |
| Token URL template | https://auth.getnoded.ai/oauth/token |
| Refresh URL | https://auth.getnoded.ai/oauth/token |
| Scopes | openid profile email noded.read noded.recommendations noded.write |
Keep the ?audience=https://api.noded.so part of the authorization URL. Without it, sign-in succeeds but Noded rejects the token.
5️⃣ Send us the callback URL. Select Create. Copilot Studio shows a callback URL (it starts with https://global.consent.azure-apim.net/). Copy it and reply to your credentials email with that URL. We add it to your client, usually within one business day, and confirm when it is done. Sign-in fails until this step is complete.
6️⃣ Create the connection. Select Next. On Add tool, select Create a new connection. 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. Then select Add to agent.
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.
| Group | What it does | Example prompt |
|---|---|---|
| Find people and accounts | Resolves 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 activity | Emails, 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 engagement | Per-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 apps | Read-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 act | Draft 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.” |
| Dates | Helpers 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. The client secret identifies your Copilot Studio agent to Noded; treat it 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. Email us to revoke the client entirely.
- 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. The callback URL from step 5 is not yet on your client. Send it to us, or check that you copied it exactly.
- Sign-in succeeds but the tool returns “Unauthorized”. Check that the authorization URL still ends in
?audience=https://api.noded.so, and 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
Why do I need a client ID and client secret from Noded?
Copilot Studio’s automatic (dynamic) OAuth registration does not complete against Noded’s sign-in service. We issue a client ID and client secret for your workspace instead, and you enter them in the Manual OAuth 2.0 option of the wizard. The sign-in itself is the same standard OAuth 2.0 authorization code flow.
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.