MCP docs add dynamic connectors and admin approval for additional connections
monday.com added a docs page on dynamic connectors, which let an account admin approve additional MCP connections and their redirect URIs. The dynamic client registration (DCR) guide was rewritten, and the registration form step was removed.
The new Dynamic connectors page is linked from the other MCP guides. Its content was not available in the crawl.
The dynamic client registration guide now says any developer can use DCR to let other monday.com accounts connect their MCP client. The earlier "Step 1: Register your integration" form submission no longer appears, and the guide now starts with authentication via DCR. Customers' admins approve the connection and its redirect URIs before it is created. The hosted MCP permission enables a separate set of pre-approved third-party agents, including Claude, ChatGPT and the other compatible MCP clients, which use the standard authorization screen.
The guides for your own OAuth app, Claude and Copilot Studio no longer say that publicly available integrations should use DCR. They now point to DCR and dynamic connectors for letting other accounts connect.
The MCP security overview adds that approval allows a connection for the account but does not grant hosted MCP access or expand user permissions. During early access, revoking an approval takes effect at the next token refresh, and an existing access token can keep working for up to 24 hours. Admins review connections under monday administration → Connectors → Dynamic Connectors.
The compatible MCP clients and Integrate with the monday MCP server pages also changed, but the details were not available. The API token and monday MCP overview pages gained links to dynamic connectors.