Connection guide

Connect your AI assistant

Your council needs to be enabled for Monitor Link before users can connect. Contact us to arrange this. After that, your IT team or the users themselves can add Monitor Link to your approved assistant.

Server URL https://link.monitorcrms.com/mcp

Claude

Add a custom connector and enter the server URL.
Leave the client ID and secret empty. Claude registers itself.
Sign in with Microsoft, Google or your Monitor CRMS password, then allow access.

ChatGPT

Ask your workspace administrator to allow custom MCP connectors, if they aren't already allowed.
Add a connector with the server URL and OAuth authentication.
Sign in and allow access when prompted.

Microsoft 365 Copilot and Copilot Studio

In Copilot Studio, add an MCP tool with the server URL and OAuth 2.0 (manual) authentication.
We'll give you the Monitor Link application details to enter.
Users use Microsoft Entra single sign-on, so there's no separate sign-in.

Azure AI Foundry, Google Gemini and other MCP clients

Add Monitor Link as a remote MCP server with these settings:

Transport: Streamable HTTP, at the server URL.
Authentication: OAuth 2.1 with dynamic client registration. Discovery is at https://link.monitorcrms.com/.well-known/oauth-authorization-server.
Users sign in and give consent in the browser the first time they connect.

If sign-in doesn't work

The sign-in page tells the user what went wrong. These are the messages you may see.

Message	What it means
“not enabled for <council>”	Monitor Link hasn't been switched on for your council yet. Contact us.
“does not allow … sign-in for the AI connector”	Your council has turned that sign-in method off. Use one of the other methods shown.
“Finish setting up multi-factor authentication”	Your council requires MFA. Complete MFA setup in Monitor CRMS first.
“more than one council”	Your email is active in more than one council. Contact us.

Before connecting, your security team may want to read security and capabilities.