Blog · October 24, 2026 · Agentdex Editorial

Cursor AI Extensions: VS Code Extensions, MCP Servers and Plugins

Cursor (Agentdex profile) is built on VS Code, so most of the extensions you already use work in it. But "Cursor extensions" now covers three different things: classic editor extensions from the Open VSX registry, MCP servers that give the agent new tools, and Cursor plugins that bundle rules, skills and MCP servers together. This guide explains each one, how to install them and where the limits are, based on Cursor's documentation as of October 24, 2026.

Key Takeaways

Cursor installs extensions from the Open VSX registry, not the Microsoft Visual Studio Marketplace, so a few Microsoft-only extensions are missing or replaced.
You can bring your VS Code extensions, themes, settings and keybindings across in one click from Cursor Settings.
MCP servers connect the agent to outside tools and data. Add them in one click or with an mcp.json file per project or globally.
Cursor plugins package skills, MCP servers, rules, commands and hooks. Marketplace plugins are open source and manually reviewed.

The three kinds of Cursor extensions

Type	What it adds	Where it comes from
Editor extensions	Languages, linters, formatters, themes, debuggers, Git tools	Open VSX registry, through Cursor's marketplace proxy
MCP servers	Tools and data the agent can call, such as GitHub, a browser or a database	One-click installs or your own mcp.json
Plugins	Bundles of skills, MCP servers, rules, commands and hooks	Cursor Marketplace, team marketplaces, community sources

Editor extensions and Open VSX

Cursor uses Open VSX, the open registry for VS Code-compatible editors. Requests go through Cursor's marketplace proxy, which runs automated malware and supply-chain checks. Most popular extensions are there, including ESLint, Prettier, GitLens, Error Lens, Python, rust-analyzer, Go, Tailwind CSS IntelliSense and Docker. Some Microsoft-only extensions are not on Open VSX (Remote - SSH and the C/C++ extension, for example), and Cursor supplies audited replacements for some of them.

One detail worth knowing: the same publisher.extension ID can point to different code on Open VSX than on the Microsoft marketplace. Check the publisher before you install, and look for the verified publisher badge.

Import your VS Code setup

Open Cursor Settings (Cmd/Ctrl+Shift+J), go to General, then Account, and use VS Code Import. It brings over your extensions, themes, settings and keybindings in one step. If Tab completion behaves oddly afterwards, the usual cause is another AI completion extension competing with Cursor's own. Disable other AI autocomplete extensions first.

Team controls

Admins can restrict which extensions people install. Cursor supports an allowed-extensions list (set in the dashboard or through MDM), a Marketplace Install Cooldown that delays installs of newly published versions by a set number of hours, and extension signature verification on Enterprise.

MCP servers

The Model Context Protocol lets Cursor's agent use outside tools: read GitHub issues, drive a browser, query a database or pull docs. Cursor supports both local servers (started with a command) and remote servers (a URL, with optional headers for authentication).

One-click: open Customize, then MCPs, and install from the list.
Per project: add a .cursor/mcp.json file to the repository so the whole team gets the same tools.
Global: add ~/.cursor/mcp.json for servers you want everywhere. When both exist, Cursor merges them and the project file takes priority.

Good starting points are the official GitHub MCP server and Microsoft's Playwright MCP server for browser automation. Only connect servers you trust. An MCP server can read data and take actions with whatever credentials you give it.

A laptop showing code with highlighted errors

Cursor plugins

Plugins are the newest layer. A plugin can package skills, MCP servers, rules, commands and hooks, and it works across the Cursor desktop app, web and CLI. Cursor supports the open Agent Plugins standard, so plugins are not locked to a single tool.

Plugins in the Cursor Marketplace must be open source, are reviewed by hand (updates are reviewed again) and cannot ship binaries. Community rules and plugins are collected at cursor.directory. On Teams and Enterprise, admins can publish internal skills and plugins to a private team marketplace, and plugins respect the organization's MCP allowlist and blocklist.

Rules: the extension most people overlook

The biggest quality gain often comes from project rules rather than another extension. Rules tell the agent your stack, conventions and things to avoid, and they live in the repository with your code. Our Cursor rules guide covers how to write them. Keep rules short and specific; long, vague rule files waste context.

A sensible starter setup

Code quality: ESLint or your language's linter, plus Prettier or your formatter, so the agent's edits match your style automatically.
Git: GitLens for history and blame when you review AI changes.
Language support: the official extension for each language you use, from Open VSX.
MCP: GitHub plus one tool you use daily, such as your issue tracker or docs.
Rules: a short project rules file before anything else.

Resist installing everything. Each extension can slow the editor, and each MCP server adds tools the agent has to choose between. Add one at a time and remove what you don't use.

Plans and limits

The extension system is part of the editor itself. What changes by plan is mostly AI usage: Free is limited, Plus ($8/month) uses Grok models only, and Premium ($30/month) adds third-party models, cloud agents and Bugbot code reviews. Team marketplaces, SSO and admin controls start on Teams ($30+ per user per month), and MCP access controls and audit logs are part of Enterprise. If you are still deciding on an editor, see our Cursor vs Copilot and Cursor alternatives guides.

FAQ

Can I use VS Code extensions in Cursor?

Yes, most of them. Cursor installs extensions from the Open VSX registry and can import your VS Code extensions in one click. A few Microsoft-only extensions aren't available on Open VSX.

Why can't I find an extension in Cursor?

It is probably published only on the Microsoft Visual Studio Marketplace, not on Open VSX. Cursor provides audited replacements for some of these. Otherwise, look for an Open VSX alternative.

How do I add an MCP server to Cursor?

Install one in one click from Customize, then MCPs, or add it to .cursor/mcp.json in your project or ~/.cursor/mcp.json for all projects. Use a command for local servers or a URL for remote ones.

What is the difference between a Cursor plugin and an extension?

An extension changes the editor itself. A plugin changes what the AI agent knows and can do, by bundling skills, rules, commands, hooks and MCP servers.

Are Cursor extensions safe?

Cursor's marketplace proxy scans extensions for malware, and Marketplace plugins are reviewed by hand. You should still check the publisher, install only what you need, and give MCP servers the minimum access they require.

Written by Agentdex Editorial. Agentdex is an independent directory reviewing AI coding tools; we are not affiliated with the companies mentioned. Prices and features are as of October 24, 2026, from official sources linked above. Always confirm on the vendor's site.