Last checked 2026-09-26
Add the server
Cursor reads MCP servers from a file called mcp.json. Choose where it goes:
~/.cursor/mcp.jsonin your home folder, to use Compliance in every project..cursor/mcp.jsonin a project, to use it in that project only. Commit the file to share the server with your team.
Add Compliance under mcpServers:
{
"mcpServers": {
"compliance": {
"url": "https://demo.mvdm.io/compliance/mcp"
}
}
}
Save the file and restart Cursor. The server then shows in Customize > MCPs.
Sign in
- Open Customize > MCPs and follow the sign-in prompt for the Compliance server. Cursor opens your browser at Auth, the mvdm.io sign-in service.
- Sign in, if you are not signed in already.
- 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.
- Press Allow, then go back to Cursor and ask its Agent 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 instead
A Personal token works in Cursor. Use one when a browser sign-in is not possible:
- Open API & Agent Access and create a Personal token. Choose its name, the Account it starts in, and when it expires.
- Copy the token. It is shown only once.
- Put the token in an environment variable, such as
COMPLIANCE_TOKEN, in your shell profile or system environment. Restart Cursor so it sees the variable. - Send the token as a header:
{
"mcpServers": {
"compliance": {
"url": "https://demo.mvdm.io/compliance/mcp",
"headers": {
"Authorization": "Bearer ${env:COMPLIANCE_TOKEN}"
}
}
}
}
Cursor fills in ${env:…} from your environment, so the token stays out of the file.
A Personal token acts as you, like a browser sign-in does. Keep it secret, and end it on API & Agent Access when you no longer need it.
Notes for Cursor
- Cursor asks for your approval before its Agent uses an MCP tool, unless your approval settings allow it.
- To stop using Compliance for a while, turn the server off in Customize > MCPs.
- If the server does not connect, open the Output panel, select MCP Logs, and look for the error.
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. Cursor's Agent can run it in the terminal. See the CLI guide.