Pieces Plugins Have Been Sunset

Pieces is no longer developing or supporting individual IDE plugins and extensions. Most existing plugins have stopped working and will not receive further updates.

All integration support is moving to the Model Context Protocol (MCP) — an open standard that lets any MCP-compatible tool connect to PiecesOS and your Long-Term Memory without a custom plugin.

If you are currently using a Pieces plugin, it may already be non-functional. **Switch to the MCP integration** for your editor or tool as soon as possible.

Why MCP?

  • One standard, many tools. MCP is supported across Cursor, VS Code, JetBrains, Claude, ChatGPT, and many more.
  • No plugin maintenance. You no longer need to install, update, or troubleshoot a separate plugin per editor.
  • Broader reach. Any tool that speaks MCP can access Pieces Long-Term Memory, Pieces Drive, and the full Pieces toolset — today and in the future.

What Should I Do?

Remove the Pieces extension from VS Code, JetBrains, Sublime Text, Neovim, JupyterLab, Visual Studio, or whichever editor you were using. Follow the [MCP Getting Started guide](/products/mcp/get-started) to connect PiecesOS to your editor via MCP. We have dedicated setup guides for [Cursor](/products/mcp/cursor), [VS Code](/products/mcp/vs-code), [GitHub Copilot](/products/mcp/github-copilot), [JetBrains](/products/mcp/jetbrains-ides), [Claude Desktop](/products/mcp/claude-desktop), and [more](/products/mcp/get-started).

Legacy Plugin Pages

The plugin docs below are kept for reference but describe unsupported, non-functional software. Do not rely on them for new setups.

Questions? Visit our support page or get started with MCP.