Last checked 2026-09-26
Add the server
VS Code reads MCP servers from a file called mcp.json. Choose where it goes:
- Your user profile, to use Compliance in every workspace. Run MCP: Open User Configuration from the Command Palette to open the file.
.vscode/mcp.jsonin a workspace, to use it in that workspace only. Commit the file to share the server with your team.
Add Compliance under servers:
{
"servers": {
"compliance": {
"type": "http",
"url": "https://demo.mvdm.io/compliance/mcp"
}
}
}
You can also run MCP: Add Server from the Command Palette. It walks you through the same settings and asks whether to add the server to your workspace or to your user profile.
Sign in
- The first time VS Code connects, the server asks it to sign in. VS Code registers itself with Auth, the mvdm.io sign-in service, and opens your browser there.
- 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 VS Code and ask Copilot in chat something about your Compliance work.
VS Code shows the sign-in under the Accounts menu. 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 VS Code. 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.
- Send the token as a header through an input variable. VS Code asks you for the token when the server first starts. It stores the token securely, and the token stays out of the file:
{
"inputs": [
{
"type": "promptString",
"id": "compliance-token",
"description": "Compliance Personal token",
"password": true
}
],
"servers": {
"compliance": {
"type": "http",
"url": "https://demo.mvdm.io/compliance/mcp",
"headers": {
"Authorization": "Bearer ${input:compliance-token}"
}
}
}
}
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 VS Code
- Copilot may ask you to confirm each tool call.
- To stop using Compliance for a while, run MCP: List Servers from the Command Palette, pick the server, and choose Disable.
The tool limit
A chat request in VS Code can have at most 128 tools turned on. Compliance offers many tools, so together with your other servers you can pass that limit. If VS Code says a request has too many tools, do one of these:
- Open the tools picker in the Chat view, and turn off tools or whole servers you do not need.
- Turn on virtual tools, so VS Code groups large tool sets for you. Set a threshold in this setting:
github.copilot.chat.virtualTools.threshold
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. Copilot can run it in the terminal. See the CLI guide.