Compliance

This is the Compliance demo. Every visitor shares this company, and it resets every night.

What you change here, everyone sees until the next reset. Email, payments, and the AI models are switched off.

Start your own trial
  • EU GDPR (2016)
  • ISO 27001:2022
  • NIS2
  • NIS2 Netherlands (Cbw, 2026)

Nothing found that matches the search criteria.

Start your own trial
SV
Sam de Vries
sam.devries@tidewell-it.example

Claude Cowork

API & Agent Access

Last checked 2026-09-26

Add the connector

Claude Cowork uses the connectors on your claude.ai account. You add Compliance once as a custom connector in Claude's settings, and Cowork picks it up at the start of each session.

The server address is:

https://demo.mvdm.io/compliance/mcp

On a Free, Pro, or Max plan

  1. In Claude, go to Customize > Connectors.
  2. Click Add custom connector.
  3. Enter a name, such as Compliance, and the server address.
  4. Leave the OAuth client settings empty. If the dialog asks you to choose, see Sign-in settings below.
  5. Click Add.

On the Free plan you can add one custom connector.

On a Team or Enterprise plan

An organization Owner in Claude adds the connector for the whole organization. Each member then connects with their own account.

  1. The organization Owner goes to Organization settings > Connectors.
  2. They select Add, then Custom. If Claude asks for the connector type, they choose Web.
  3. They enter the server address and leave the OAuth client settings empty, or choose as in Sign-in settings below.
  4. They click Add.
  5. Each member goes to Customize > Connectors and finds the connector with the Custom label.

If you do not have that role in Claude, ask your organization Owner to add the connector.

Sign-in settings

In some organizations the Add custom connector dialog has two steps and asks you to choose:

  • For Authentication, choose Sign in now or Sign in when needed. Do not choose No sign-in: Compliance needs each person to sign in.
  • For OAuth client, choose Use Claude's published identity or Register automatically. Auth supports both.

Sign in

  1. In Customize > Connectors, click Connect on the Compliance connector. Your browser opens Auth, the mvdm.io sign-in service.
  2. Sign in, if you are not signed in already.
  3. Auth shows a consent page. It names the Agent and warns that the Agent gets all your power, in every Account you belong to, billing and the License included. It asks which Account the Agent starts in.
  4. Press Allow, then go back to Cowork and ask it something about your Compliance work.

You can see and end every connection on API & Agent Access. An ended connection fails on its next call.

A Personal token does not work here

Claude Cowork uses the browser sign-in only. A Personal token does not work for it.

Claude's connector settings have a place for request headers, but it is in beta for a limited set of organizations. And on a connector that signs in through the browser, Claude does not let you set the Authorization header, because the sign-in uses it. So each person connects with their own browser sign-in.

Notes for Claude Cowork

  • Cowork loads the connectors enabled for your claude.ai account, synced at the start of each session. Manage them from Customize in the sidebar.
  • You can turn the connector on or off for one conversation: click + in the chat, select Connectors, and use its toggle.
  • You cannot change a connector's sign-in settings after you add it. To change them, remove the connector and add it again.

What to expect

  • Browser handoff. Some acts need you in the browser, such as anything that costs money or accepting the Legal terms. Your Agent then shows you a link. Open it, check what is filled in, and confirm. If you do not open the link, nothing happens.
  • Upload link. A tool call cannot carry a file, so your Agent asks Compliance for an Upload link, a one-time address for one file. The Agent sends the file there itself, often with curl, or it shows you the link so that you can pick the file in your browser. The link expires after a few minutes.
  • One Account at a time. Your Agent starts in the Account you chose on the consent page, or the one you chose for your Personal token. Every answer says which Account it acted in. Ask your Agent to switch, and it moves to another Account you belong to.
  • Rate limit. Each User has a limit on calls per minute, shared by all of your Agents and scripts. Over the limit, a call fails and says how many seconds to wait.

Another way in

Compliance also has a command-line tool, the Compliance CLI. It suits Agents that run commands, and scripts. See the CLI guide.

Are you sure?

This action cannot be reverted.

Leave this page?

Your changes on this form are not saved. If you leave, they are lost.