add-mcp-server

Add and configure MCP servers for the pi agent.

437|40|Updated Jan 31, 2026

Search Tags:#developer tools #mcp #http #server configuration #stdio #pi agent

Ready to run

npx skills add https://github.com/HazAT/pi-config --skill add-mcp-server

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-mcp-server
Source: https://github.com/HazAT/pi-config/tree/main/skills/add-mcp-server
Command: npx skills add https://github.com/HazAT/pi-config --skill add-mcp-server

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of adding and configuring Message Communication Protocol (MCP) servers for the pi agent, ensuring seamless integration with various backend services.

Core Features & Use Cases

Flexible Server Configuration: Supports both global and project-local MCP server setups.
Multiple Connection Types: Handles both stdio (local command execution) and HTTP (remote URL) connections.
Detailed Configuration Options: Allows for specifying commands, arguments, environment variables, URLs, headers, authentication, and lifecycle management.
Use Case: You need to connect pi to a new internal development tool that exposes an MCP interface via a local command. This skill will guide you through setting up the command, any necessary arguments, and environment variables, then verify the connection.

Quick Start

Use the add-mcp-server skill to add a new global MCP server named 'dev-tool' using the command 'npx -y @my-org/mcp-dev-tool'.

Frequently Asked Questions about add-mcp-server

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

FAQPage Schema

How do I configure an MCP server for the pi agent?▼

To configure an MCP server for the pi agent, you can use this skill to add servers at either a global or project-local scope, specifying connection details like commands, environment variables, or URLs for seamless backend integration.

What is the difference between stdio and HTTP MCP server connections?▼

Stdio MCP connections execute local commands with specific arguments and environment variables, while HTTP connections configure remote URLs with headers and authentication, both allowing the pi agent to communicate with backend services.

Can I set environment variables and headers when adding an MCP server?▼

Yes, you can set environment variables for stdio connections and configure headers and authentication for HTTP connections, ensuring the pi agent has the necessary context and security credentials to access the MCP server.

Does the MCP server configuration process verify the connection status?▼

Yes, the MCP server configuration process verifies the connection and reports the status, ensuring that the pi agent successfully reaches the backend service through the specified stdio command or HTTP URL.

What's the best way to add a local development tool as an MCP server?▼

The best way to add a local development tool is to configure it as a stdio MCP server, providing the execution command like 'npx -y @my-org/mcp-dev-tool' along with any required arguments and environment variables.