Pieces + Cursor
Access your Pieces Long-Term Memory from inside the Cursor chat, powered by the Pieces MCP server. Bring your Long-Term Memory into your agent chats, allowing Cursor to suggest and make code changes based on the context captured across all your activities in your developer workflow.
Cursor
Cursor + Pieces
Access your Long-Term Memories from the Cursor agent chat
Connect the Pieces MCP server to Cursor, allowing your Long-Term memory to be queried from inside the agent chat. Mix your day to day coding prompts with asking Pieces questions based on your activities.
Prompt by time range or source application
Pieces inside Cursor supports time-based and source-based queries, allowing you to ask questions like “What was I doing yesterday?” or “Summarize all my emails from the last week in Superhuman”.
Use the responses from Pieces to update code
Use the responses from Pieces into your Cursor agentic workflows. Ask Cursor to retrieve details of a code change you were discussing with a colleague from the Pieces Long-Term memory, and have the agent implement the changes automatically.
Frequently asked questions
How do I connect the Pieces MCP server to Cursor?
Pieces supports the SSE transport for MCP, and you can get the URL from the PiecesOS menu bar. It will be something like http://localhost:39300/model_context_protocol/2024-11-05/sse, but the port may change to avoid clashing with other locally running applications. Check the guide on configuring Cursor in our documentation.
What does the Pieces Cursor integration actually do?
What LLM does Pieces use to return a response to the request from Cursor?
Does the Pieces share all my memories to Cursor by default?
What chat mode is Pieces available in?