add-pi-mcp-server

Convert unstructured MCP details into a Pi MCP config file.

Updated Jun 7, 2025
One-click install
npx skills add https://github.com/erazemk/dotfiles --skill add-pi-mcp-server
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-pi-mcp-server
Source: https://github.com/erazemk/dotfiles/tree/main/pi/agent/skills/add-pi-mcp-server
Command: npx skills add https://github.com/erazemk/dotfiles --skill add-pi-mcp-server

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts unstructured MCP server details into a Pi MCP configuration, enabling quick setup of Pi-integrated MCP servers without manual configuration.

Core Features & Use Cases

  • Parse unstructured MCP details from prose, copied docs, or JSON blocks and extract server name, transport type, and tool list.
  • Probe the MCP server with npx mcporter list to discover exposed tools and validate availability before writing config.
  • Write or merge a Pi MCP config at ~/.pi/agent/mcp.json with directTools configured (subset or full exposure) and always apply lifecycle: keep-alive.

Quick Start

Provide MCP details in any format and I will generate a Pi MCP config at ~/.pi/agent/mcp.json after probing with mcporter.

Frequently Asked Questions about add-pi-mcp-server

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure an MCP server in Pi from pasted documentation or JSON?

To configure an MCP server in Pi, provide unstructured details like prose or JSON blocks. The setup parses server name and transport type, probes with npx mcporter list, and writes the final config to ~/.pi/agent/mcp.json.

What's the best way to discover exposed tools before adding an MCP server configuration?

Discovering exposed tools before adding an MCP server configuration is done by probing the server with npx mcporter list. This validates tool availability and generates the directTools list for the Pi config file.

Does Pi MCP configuration support both stdio and HTTP transport types?

Pi MCP configuration supports both stdio and HTTP transport types to ensure deterministic behavior. The parsing logic extracts the transport type from your input details and applies it during the config generation process.

How do I merge a new MCP server config with an existing Pi agent configuration?

To merge a new MCP server config with an existing Pi agent configuration, the setup writes to ~/.pi/agent/mcp.json. It combines new server details with existing entries and always sets the lifecycle to keep-alive.

What happens if required MCP setup fields are missing from my pasted documentation?

If required MCP setup fields are missing from your pasted documentation, the configuration process will prompt you to supply them. This ensures the generated Pi config maintains deterministic stdio or HTTP transport behavior.

Can I control which tools are exposed when setting up a Pi MCP server?

You can control which tools are exposed when setting up a Pi MCP server by configuring directTools. The setup writes a subset or full tool exposure list to the config file after probing the server with npx mcporter list.