Installation

Install mcpi on macOS and know where everything ends up

Requirements

  • macOS (Apple silicon or Intel)
  • For stdio servers that run via npx, uvx, or bunx: the matching runtime installed the way your shell finds it

Install

1

Build it

Clone the repository and run just app, which runs dx serve --package mcpi --platform desktop. You need a Rust toolchain and the dx CLI.

2

First launch

On first launch mcpi creates its local store and shows an empty server library — add your first server and you're inspecting.

Where things end up

What Where
Servers, snapshots, history, collections ~/Library/Application Support/mcpi (one SQLite file)
OAuth tokens, API keys macOS Keychain, keyed per saved server

A note on PATH

Apps launched from Finder do not inherit your shell's PATH, which is the single most common reason a stdio MCP server fails to spawn in other tools. mcpi resolves your login shell's real PATH once and injects it into every spawned server, so npx-style commands work the same as they do in your terminal.

Navigation