I Tried Cursor’s New Plugin Marketplace (Notion, Figma, Team Kit): First Impressions
What plugins include (MCP, skills, prompts, hooks), how setup feels, and my first impressions without the hype...
The Cursor team just announced their marketplace/plugin system in a new blog post: https://cursor.com/blog/marketplace
After I saw the blog post on Cursor’s LinkedIn post, I wanted to give it a try and set up three plugins: Notion, Figma, and Cursor Team Kit.
So, I decided to share my first experiences using them, without hype :)
🤝 This post is sponsored by Jotform!
Jotform AI Agents lets developers, PMs, and product teams build and deploy AI-powered agents (for customer service, data collection, and workflow automation) without writing a single line of backend code. Whether you’re prototyping an internal tool or scaling a customer-facing pipeline, it’s a fast, no-hassle way to bring AI into your product. Try it for free →
What is a Plugin, anyway?
A plugin is basically a bundled structure of MCP servers, skills, subagents, rules, and hooks, and it provides a way to benefit from them together.
Cursor provides a Marketplace where you can check the currently accessible plugins (https://cursor.com/marketplace):
You can select a plugin you want to use, then you’ll see the “Add to Cursor” button. It will directly set up the plugin in your Cursor IDE:
On that page, you can see the plugin’s MCP Servers, Skills, Subagents and Hooks. For example, the AWS plugin provides a single skill and three MCP Servers, which you need to connect in the MCP Servers section in Cursor (as described below).
Configuring Plugin MCP Servers
After you add a plugin, if you want to use the relevant MCP servers, open Cursor Settings → Tools & MCP Servers, and connect to the relevant MCP servers with a single click:
You should see the Connect button on the relevant plugin MCP server. Once you click it, Cursor redirects you to the related MCP server connection page. You’ll see the consent screen, and once you approve the connection, it sets up authentication for the relevant tools.
Then, you’ll be able to use the plugin MCP servers like other MCP servers. Additionally, with this plugin system, you’ll have extra skills, subagents, hooks, and so on.
So, once you use an MCP server, for example Figma, it will use the defined skills (pre-integrated with the plugin), follow the instructions intelligently, and return a better result. Here’s an example screenshot from my tests:
According to my prompt, it used the Figma plugin skill intelligently, understood it should use the Figma MCP tool, and implemented what I asked for. You can see the used skill on the Figma plugin details in the Cursor IDE:
Using Prompts of Plugin MCP Servers
If your configured plugin MCP servers provide prompts, like the create_design_system_rules prompt template for the Figma MCP server:
You can call them directly with the plugin/<prompt> call in the chat section like before:
Conclusion
Cursor’s Plugins/Marketplace includes nice pre-integrations with MCP servers, skills, subagents, prompts, and more, and it can be easily configured and used in your daily workflow.
But they’re not a brand new breakthrough that you couldn’t do before this system. Cursor is bundling these pieces together and making them easier to discover and more productive to adopt.
If you haven’t tried it yet, it feels more logical to install a plugin and then connect the MCP server, rather than starting from scratch and wiring everything manually.
Thanks for reading, see you in the next one :)
Thanks for useful article :)
I will planned to try some Cursor plugins on next weekend 👍