Model Context Protocol (MCP) Settings

Access server URLs and documentation for integrating Pieces Long-Term Memory with Cursor, GitHub Copilot, and other tools that support the Model Context Protocol. The MCP server enables connectivity between Large Language Models (LLMs) and your personal context stored by the Long-Term Memory Engine (LTM-2.7).

To access MCP settings, click your User Profile in the top left, then hover over Settings and select MCP.

Model Context Protocol settings showing server URLs and documentation

Model Context Protocol (MCP) settings showing server URLs and View Documentation option

Available Servers

Copy the server URLs to configure MCP integrations in compatible IDEs and code editors. Multiple server URLs are available, including the latest schema version and previous versions for compatibility.

Understanding Server URLs

The MCP settings display server URLs that your development tools or AI applications, such as Cursor or GitHub Copilot, will use to communicate directly with your local PiecesOS MCP server.

Copy the server URL below and paste it into your MCP client configuration. The latest schema version may not be compatible with all MCP clients yet. If you experience connection issues, try using an earlier version or restarting your MCP client. For the best results, try using with Cursor or Claude.

Copying Server URLs

Click your `User Profile` in the top left, then hover over `Settings` and select `MCP`. In the *Available Servers* section, you'll see server URLs displayed, each with a Copy Icon to the right. The latest schema URL is marked with a blue "LATEST SCHEMA" badge. Click the `Copy Icon` next to the URL to copy it to your clipboard. The URL format is `http://localhost:39300/model_context_protocol/2025-03-26/mcp` with the release date displayed below it. If you need compatibility with older MCP clients, you can copy a previous version URL (e.g., `http://localhost:39300/model_context_protocol/2024-11-05/sse`). Click the `Copy Icon` next to the URL you need. Paste the copied URL into your IDE or tool's MCP configuration. Use the latest schema URL for the most up-to-date features, or use an earlier version if you encounter compatibility issues. The release date displayed under each server URL indicates when that schema version was released. The latest schema version provides the most current features, but older versions may be more compatible with certain MCP clients.

View Documentation

Access detailed guides that explain how to leverage MCP integrations with popular development environments, such as Cursor and GitHub Copilot.

Opening MCP Documentation

Click your `User Profile` in the top left, then hover over `Settings` and select `MCP`. Scroll to the *View Documentation* section, which displays: "Learn how to use Long-Term Memories with Cursor, GitHub Copilot and other tools using our MCP server." Click the `Documentation Icon` (book icon) to open the MCP documentation, which covers setup instructions, example scenarios, and troubleshooting tips for efficient MCP usage.

The documentation provides comprehensive guides on:

  • Setting Up Integrations: Step-by-step instructions for configuring MCP in Cursor, GitHub Copilot, and other tools
  • Use Cases: Examples of how MCP enhances your coding and debugging experiences
  • Troubleshooting: Solutions for common integration issues and configuration problems

Example Use Cases

MCP enhances your coding and debugging experiences in several ways:

  • Context-Rich Debugging: Instantly retrieve logs, historical debugging notes, or team discussions directly from PiecesOS when troubleshooting within Cursor
  • Contextual Queries: Access historical code implementations, error resolutions, or previously encountered bugs within GitHub Copilot for quicker coding solutions

For more use cases and detailed setup instructions, refer to the MCP documentation.

Next Steps

Now that you understand how to access MCP server URLs and documentation, learn how to set up MCP with Cursor or integrate with GitHub Copilot to start using Pieces Long-Term Memory in your development workflow.