Skip to main content
Cursor connects to Vacademy MCP as a remote server. You add the server URL to Cursor’s MCP settings file and sign in through your browser. The hint in your admin portal mentions claude mcp add. That command is for Claude Code. Cursor uses mcp.json, as shown here.
Menus may move. These steps match Cursor’s MCP documentation as of October 2026. See Model Context Protocol in Cursor.

Add the server

Copy the server URL from Settings → MCP Server in your admin portal. Then add it to one of Cursor’s mcp.json files:
~/.cursor/mcp.json
If the file already has other servers, add the vacademy entry next to them inside mcpServers. The file holds only the URL, never a token, so a project file is safe to commit. Each person still signs in as themselves.

Sign in

1

Open the server in Cursor

Cursor picks up the new server. Find it where Cursor lists MCP servers (at the time of writing, Customize in the sidebar) and make sure it is enabled.
2

Approve in your browser

When Cursor starts the sign-in, a browser tab opens on your institute’s admin portal. Sign in with your own account and click Approve.
3

Check the connection

In the Agent chat, ask:
Cursor calls the whoami tool to answer. In Cursor’s MCP settings, the server should show its tools. Only whoami? Every area is Off for your role.
No client ID is needed. Cursor registers itself.

Approvals

By default, Cursor asks before each MCP tool runs. Keep it that way for edit tools. If you use an auto-approve or allowlist mode, allow only tools that read. On top of Cursor’s approval, live edits that are turned on separately (opt-in), and anything that contacts a lead, show a preview and wait for your yes in the chat. A few edits apply directly: invite page and form edits (Courses Edit), and a course’s images or intro video. See Confirmations and Risk levels.

Good uses in Cursor

Cursor is handy when you have files open, such as a design export, a syllabus or a CSV.

Using a fixed client ID

Only needed if your organisation requires every app to use a pre-registered client.
1

Admin: create a client ID for Cursor

In Settings → MCP Server → Client IDs for other apps, click Add a client ID for another app. Name it Cursor and add Cursor’s redirect URLs, separated by a comma:
Cursor documents these two addresses (the desktop app and Cursor’s web agents). Check Cursor’s MCP docs in case they have changed.
2

Add the client ID to mcp.json

~/.cursor/mcp.json
There is no client secret.