Pistachio

You can run Pistachio MCP Server to manage remote projects, run tests, and search assets for your mobile development workflow. It exposes an MCP endpoint to handle client requests and offers a development workflow that supports hot reload and local testing while providing a production-ready build path.

How to use

Connect to the MCP endpoint from your MCP client to establish a stream for receiving messages and to send requests. Use the HTTP endpoint for remote interactions, or run the server locally in development mode to test commands and prompts. When using the HTTP endpoint, you will access the MCP surface at the message path and interact through the standard MCP flow. For local development, start the server and interact with it via the same endpoint URL or through the development runtime commands.

How to install

Follow these concrete steps to set up Pistachio MCP Server from scratch. Ensure you meet the prerequisites before starting.

# 1. Clone the repository
git clone <repository-url>
cd pistachio-mcp

# 2. Install Yarn (v4.10.3 or compatible)
# Install Yarn globally if needed
npm install -g yarn

# Or enable Corepack and prepare Yarn
corepack enable
corepack prepare yarn@4.10.3 --activate

# 3. Install dependencies
yarn install

Configure environment and run

Set up environment variables for development and production, then build and run the server. The following configuration options are optional but recommended for local development and testing.

# Optional: Set custom port (default: 3001)
PORT=3001

# Optional: Set number of worker threads (default: 2)
NUM_WORKERS=2

# Optional: Set Node environment
NODE_ENV=development

# Optional: Firebase emulator configuration (for development)
FIREBASE_AUTH_EMULATOR_HOST=localhost:9099
FIRESTORE_EMULATOR_HOST=localhost:8080

# Optional: Google Cloud Storage bucket for weekly expiring assets
GCS_BUCKET_WEEKLY_EXPIRING=dev-pistachio-assets-weekly-expiring

Build and verify

Build the TypeScript sources to produce a production-ready set of JavaScript files, then verify that tests pass and the server can start.

yarn build

yarn test:run

Run in development and production modes

You can run the server in development mode with hot reload to iterate quickly. For a production run, build first and then start the compiled server.

yarn dev
# or
# Development server uses port 3001 by default unless PORT is set

# Production flow
yarn build
node dist/index.js

Server endpoint and access

The MCP endpoint is exposed at the /message path. Use this to establish an SSE stream for incoming messages on GET, to send MCP requests on POST, and to handle CORS preflight on OPTIONS. Example endpoint location for local development is http://localhost:3001/message.

Available tools

search_image

Search for images using the MCP tools to locate assets quickly.

search_icon

Search for icons within the asset repository for UI components.

create_remote_project

Create and manage remote projects through the MCP server.

remote_kdoctor

Run kdoctor diagnostics remotely to assess project health.

remote_clean_project

Clean up and reset a remote project as needed.

remote_test_android

Execute Android tests remotely to validate builds.