MCP Launchpad (Your gateway to ALL MCPs!)
Documents the MCP Launchpad CLI for discovering and calling tools across multiple MCP servers with a discover-before-call workflow.
What this file does
Documents the MCP Launchpad CLI for discovering and calling tools across multiple MCP servers with a discover-before-call workflow.
When to use it
- You need a unified CLI to search and call tools from many MCP servers
- You want to avoid guessing tool names by searching first
- You need troubleshooting commands for MCP server connections and OAuth
- You manage multiple MCP configs and need to switch between them
Assumes this stack
MCP Launchpad (Your gateway to ALL MCPs!)
You have access to the MCP Launchpad (mcpl), a unified CLI for discovering and executing tools from multiple MCP servers. The user may configure and change their MCP configuration at any time. So if your task requires a tool or functionality outside of your current capabilities, it's critical that you always check the MCP Launchpad for available tools that may be useful.
Important: Always Discover Before Calling
Tool names vary between MCP servers. Never guess tool names - always discover them first.
If you're unsure of the tool name, always search first. The mcpl search command is the most efficient way to find relevant tools across all MCP servers.
Recommended Workflow
-
Search first to find the right tool (shows required params):
mcpl search "list projects" -
Call with required params:
mcpl call vercel list_projects '{"teamId": "team_xxx"}'
Alternative: List Server Tools
If you know which server to use but not the tool name:
mcpl list vercel # Shows all tools with required params
Get Example Calls
For complex tools, use inspect --example to get a ready-to-use example:
mcpl inspect sentry search_issues --example
# Shows: mcpl call sentry search_issues '{"organizationSlug": "<organizationSlug>", ...}'
Error Recovery
If a tool call fails, mcpl provides helpful suggestions:
- Tool not found: Shows similar tool names from that server
- Missing parameters: Shows required params and an example call
- Validation errors: Shows expected parameter types
Troubleshooting Commands
mcpl verify # Test all server connections
mcpl session status # Check daemon and server connection status
mcpl session stop # Restart daemon (stops current, auto-restarts on next call)
mcpl config # Show current configuration
mcpl call <server> <tool> '{}' --no-daemon # Bypass daemon for debugging
mcpl auth status # Check OAuth authentication status
mcpl auth login <server> # Authenticate with OAuth-protected server
Common Issues
- Server not connecting: Run
mcpl verifyto test connections - Stale connections: Run
mcpl session stopthen retry - Timeout errors: Server may be slow; increase with
MCPL_CONNECTION_TIMEOUT=120 - OAuth authentication required: Run
mcpl auth login <server>to authenticate - Token expired: Run
mcpl auth login <server> --forceto re-authenticate - Multiple configs found: Run
mcpl config files --selectto choose which to use - Wrong config active: Run
mcpl config filesto see status and adjust
Quick Reference
# Show help
mcpl --help
# Find tools
mcpl search "<query>" # Search all tools (shows required params, returns 5 by default)
mcpl search "<query>" --limit 10 # Get more results
mcpl list # List all MCP servers
mcpl list <server> # List tools for a server (shows required params)
# Get tool details
mcpl inspect <server> <tool> # Full schema
mcpl inspect <server> <tool> --example # Schema + example call
# Execute tools
mcpl call <server> <tool> '{}' # No arguments
mcpl call <server> <tool> '{"param": "value"}' # With arguments
# Verify servers
mcpl verify # Test all servers are working
# Config management (when multiple configs exist)
mcpl config files # View active/inactive configs
mcpl config files --select # Interactive selection
What's inside
7 sections covering workflow, search, call, inspect, error recovery, troubleshooting, and quick reference with 15+ command examples
Change this for your project
- Replace
kenneth-liao/mcp-launchpadwith your own repository name if forking - Replace
vercelandsentryserver names with your own MCP servers in examples
Where it goes
Save as CLAUDE.md in your repository root. Claude Code reads it automatically at the start of every session.
Worth borrowing
- Always search before calling to discover tool names and required params
- Provide an
inspect --examplecommand to generate ready-to-use calls for complex tools - Include a dedicated error recovery section with specific troubleshooting commands
Related Documents
Code indexing for AI agents: summarization strategies and evaluation systems
Synthesises 2024-2025 research on code indexing for AI agents, covering summarisation strategies, hybrid retrieval architectures, and evaluation benchmarks.
write-script
Guides an AI through writing a YouTube video script with strict structural, language, and quiz rules for a survival channel.
Claude AI Git Workflow Integration
Recommends using the git-ai-commit CLI tool for AI-generated commit messages instead of manual ones.
Missing Business Agents Research — FLUXION 2026
Identifies 12 missing business operations agents for an indie software company and ranks them by impact and effort with €0 implementation plans.