Get Started

Integrating the Pieces MCP with Rovo Dev CLI brings your workflow context directly into Atlassian's AI tool. Rovo Dev CLI supports stdio, SSE, and Streamable HTTP for flexible setup.

Prerequisites

There are two prerequisites for integrating Pieces with Rovo Dev CLI as an MCP—an active instance of PiecesOS and the fully-enabled Long-Term Memory engine.

Make sure that PiecesOS is installed and running. This is *required* for the MCP server to communicate with your workflow data. Enable the Long-Term Memory Engine (LTM-2.7) through the Pieces Desktop App or the [PiecesOS Quick Menu](/products/core-dependencies/pieces-os/quick-menu) in your toolbar.

Installing PiecesOS & Configuring Permissions

Follow the instructions below for a detailed guide on setting up and configuring PiecesOS to correctly pass captured workflow context to the Pieces MCP server.

Setting Up Rovo Dev CLI

Rovo Dev CLI stores its MCP configuration in ~/.rovodev/mcp.json. It uses a servers root key with a transport field (not type).

Config File Location

Platform Path
All platforms ~/.rovodev/mcp.json

Local Setup (Streamable HTTP — recommended)

Edit ~/.rovodev/mcp.json:

{
  "servers": {
    "pieces": {
      "name": "Pieces LTM",
      "transport": "http",
      "url": "http://localhost:39300/model_context_protocol/2025-03-26/mcp"
    }
  }
}

Local Setup (SSE)

{
  "servers": {
    "pieces": {
      "name": "Pieces LTM",
      "transport": "sse",
      "url": "http://localhost:39300/model_context_protocol/2024-11-05/sse"
    }
  }
}

Opening the Config in Your Editor

Run this command to open the config file in your default editor:

acli rovodev mcp

Using Pieces MCP Server in Rovo Dev CLI

Once integrated, you can utilize Pieces LTM directly in Rovo Dev sessions.

Start a Rovo Dev session from your terminal. Run `/mcp list` to see configured servers and their status. Ask: *"What Pieces tools do you have?"* or *"What was I working on yesterday?"*

Managing Servers in Interactive Mode

Within a Rovo Dev session, use the /mcp command to open an interactive interface showing:

  • Configured servers and their status
  • Available tools from each server
  • Enable/disable toggles

Updating

Edit ~/.rovodev/mcp.json (via acli rovodev mcp or directly), update the URL, and restart the Rovo Dev session.

Troubleshooting

If you're experiencing issues integrating Pieces MCP with Rovo Dev CLI:

  1. Verify PiecesOS Status: Ensure PiecesOS is actively running on your system.

  2. Use transport, Not type: Rovo Dev CLI uses the transport key (not type) for the transport type.

  3. Config File Not Found: Create ~/.rovodev/ and ~/.rovodev/mcp.json manually if the directory does not exist.

  4. Restart Session: Restart the Rovo Dev session after editing the config.

  5. Atlassian OAuth: Pieces does not require Atlassian OAuth. If prompted, this is for the Atlassian Rovo MCP Server, not Pieces.

You're now set to enhance your Rovo Dev CLI workflow with powerful context retrieval through Pieces MCP. Happy coding!