mcp-launchpad

MCP Launchpad provides a lightweight CLI (mcpl) to discover, inspect, and execute tools exposed by multiple MCP servers. It scans configured servers, aggregates available tools, and lets you run them from a single interface. Use mcpl search to find tools across all servers, mcpl list to view configured servers, and mcpl call <server> <tool> to execute a tool with JSON arguments. You can inspect a tool to see its full schema and example usage, and you can enable OAuth-protected servers after authenticating them. This setup enables dynamic tool discovery and execution without manually invoking each server.

Prerequisites:

• Python 3.13+ installed
• uv (Python package and environment manager) installed
• Internet access to install and fetch MCP servers

Installation steps:

1. Install the uv CLI if you haven’t already (the documentation linked in the README provides install instructions).

uv tool install https://github.com/kenneth-liao/mcp-launchpad.git

2. Verify installation by checking the mcpl helper:

mcpl --help

3. Prepare a project directory (or use global config paths) and set up your mcp.json as described in the README. You can start with the example configuration and customize paths to your local MCP servers.
4. Optionally set environment variables or create a .env file as described for OAuth and server-specific tokens.

Notes and tips:

• MCP Launchpad discovers config files in this order: ./mcp.json, .claude/mcp.json, and ~/.claude/mcp.json. When multiple are found, you’ll be prompted to select which to use.
• For servers requiring OAuth, you must authenticate them before agents can use them. Use mcpl auth login <server>, then mcpl auth status to verify.
• Environment variables are expanded using ${VAR} syntax and can be loaded from ~/.claude/.env or ./ .env files. Ensure sensitive tokens are kept secure and not committed to version control.
• If you modify config files, you can refresh the server list with mcpl list --refresh.
• The configuration supports multiple servers with distinct commands (npx, uvx, etc.). You can mix different runtimes as needed for your environment.