💡
Prefer a simpler setup?
Copilot Studio supports a default monday.com connector. Use that path when you want the fastest connection — no custom OAuth app required. See Connect monday MCP with Microsoft Copilot Studio.

Use this guide when you want Copilot Studio connected to monday.com through your own OAuth app, instead of the hosted one-click / default connector. You get the same MCP tools in your agent, with tighter control over who can connect and what the connection is allowed to do.

For the full organization-wide pattern (any MCP client, authorization flow details, and approach comparison), see Control MCP access with your own OAuth app.

Why use a custom app with Copilot Studio

By default, AI assistants can connect via monday.com's hosted MCP connector: users click Connect, sign in, and they're done. That path is fastest, but it's all-or-nothing — once enabled, any user who can log in, from any MCP-compatible client, can connect, and the connection inherits that user's full monday.com permissions.

A custom OAuth app is the right choice when you need to:

Limit scopes — Cap MCP actions with app-level permission scopes (for example boards:read only), even if the user has broader permissions in monday.com
Choose who connects — Share Client ID and Client Secret only with approved builders/users; everyone else stays locked out
Prefer Copilot Studio specifically — Route access through credentials you control, rather than leaving the hosted connector open to any MCP client
Revoke cleanly — Remove one user, or rotate the Client Secret to cut off everyone, without disrupting unrelated integrations
Keep a separate audit trail — Authorized users and activity appear under your app in the developer platform

This path is also appropriate while you're developing a private or org-internal MCP setup. Publicly available integrations should use dynamic client registration instead.

Before you start

You'll need:

Permission to create an app in the monday.com Developer Center
Admin access to turn off the hosted MCP connector for your account (so users can't bypass your app)
A Copilot Studio agent where you can add tools

Step 1: Create your OAuth app in monday.com

The monday MCP server uses the standard OAuth 2.0 Authorization Code Grant, with monday.com as the identity provider.

Create your app

Log in to your monday.com account. Click your profile picture in the top-right corner and select Developers to open the Developer Center
Click + Create app in the top-right corner
Enter an App Name and App Slug, then click Create app

Configure OAuth settings

In the left sidebar under Build, click OAuth & Permissions
On the Scopes tab, select only the permission scopes your integration needs — these scopes cap what the MCP connection can do (add all during testing if needed)
Leave Redirect URLs for Step 3 — Copilot Studio generates the redirect URI after you start adding the MCP tool. You'll paste that URL back into monday.com before finishing authorization

Retrieve your credentials

Go to General Settings in the left sidebar of your app
Scroll down to the App Credentials section and copy your Client ID and Client Secret

❗️
NOTE
Your client secret is a secret. Never share it or add it to source code others can access. You can regenerate it from the app's settings if it's ever compromised.

Step 2: Turn off the hosted MCP connector

In your monday.com admin settings, disable the built-in hosted MCP connector. This step matters: as long as it's on, users can bypass your app and connect the old way.

Step 3: Add a Model Context Protocol tool in Copilot Studio

Open your agent in Copilot Studio
Go to the Tools tab and click Add a tool
Choose Model Context Protocol
Enter the server details:

Field	Value
Server name	`monday MCP` (names can't include a period)
Server description	`monday.com project management & CRM for projects, tasks, portfolios, boards, workflows, milestones, dependencies, forms, dashboards, cross-project portfolio status, and critical paths.`
Server URL	`https://mcp.monday.com/mcp` (the common hosted monday MCP endpoint)

Under Authentication, select OAuth 2.0, then set Type to Manual

Fill in the OAuth fields. Use values like the examples below — replace the Client ID with yours:

Field	What to enter	Example
Authorization URL	monday authorize endpoint with your Client ID	`https://auth.monday.com/oauth2/authorize?client_id=38143d6bd05d57a74ed5e99942b24ttt`
Token URL	monday token endpoint	`https://auth.monday.com/oauth2/token`
Refresh URL	No separate refresh endpoint today — reuse the token URL	`https://auth.monday.com/oauth2/token`

After submitting, copy the Redirect URI Copilot Studio shows for this connector. It looks similar to:

https://global.consent.azure-apim.net/redirect/cr7d9-5fmonday-20mcp-20test-2077-5f0f516cbecf05asda

Your URI will be unique to your connector — use the one Copilot Studio provides, not this example string as-is.

Step 4: Add the Copilot Studio redirect URI in monday.com

Back in your monday.com app, open OAuth & Permissions → Redirect URLs
Paste the Redirect URI from Copilot Studio and click Save

The redirect must match exactly. If it doesn't, authorization fails (for example, missing state or redirect mismatch errors from Azure consent).

Step 5: Complete authorization and verify

Finish adding the tool in Copilot Studio and run through the OAuth consent screen
In Copilot Studio, confirm the MCP tool is available on the agent and can call monday.com successfully

💡
Recommendation: After the MCP server is connected, review the available tools in Copilot Studio and disable any tools you don't want the agent to use. Leaving only the tools your agent needs reduces accidental writes, keeps prompts more focused, and complements the permission scopes on your OAuth app.

What happens after you connect

All MCP tool calls from Copilot Studio run as the authenticated monday.com user, limited by both that user's platform permissions and the scopes on your OAuth app. The MCP token can't exceed either boundary — it doesn't grant permissions the user lacks, and it can't use permissions the app didn't request.

Related resources: