Pieces MCP Server

Turn your Pieces Long-Term Memory into an AGENTS.md your coding agents can read.

Local serverstdioGo

What is the Pieces MCP Server?

Turn your Pieces Long-Term Memory into an AGENTS.md your coding agents can read.

What it actually does

PiecesOS records what you work on all day. Your coding agent starts every session with none of it. This CLI reads your memory over MCP and writes the parts that belong to a repository into its context file, so the next agent already knows why the code looks the way it does.

Agent context files have become the standard way to tell Claude Code, Cursor or Copilot how a project works. Almost nobody keeps them current, because writing down what you already know is the first task to get dropped. Meanwhile PiecesOS has been quietly recording the decisions, the bugs and the dead ends the whole time.

Configuration

  • PiecesOS running locally with its MCP server enabled, on the default port 39300 - Node.js 20.11 or newer - A git repository to write into

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

How to install the Pieces MCP Server

{
  "mcpServers": {
    "pieces": {
      "command": "npx",
      "args": ["-y", "pieces-to-agents"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • PiecesOS running locally with its MCP server enabled, on the default port 39300 - Node.js 20.11 or newer - A git repository to write into

Example prompts to try

  • “Use Pieces to Principle.”
  • “Use Pieces to Flag.”

Frequently asked questions

Turn your Pieces Long-Term Memory into an AGENTS.md your coding agents can read. Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.