mcp-to-cli

Convert MCP definitions into standalone CLIs using mcporter.

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/leolionart/claude-skills --skill mcp-to-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-to-cli
Source: https://github.com/leolionart/claude-skills/tree/main/plugins/mcp-to-cli/skills/mcp-to-cli
Command: npx skills add https://github.com/leolionart/claude-skills --skill mcp-to-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts MCP definitions into standalone CLIs or one-off tool invocations, enabling you to run MCP tools without needing to register the server in Claude Code.

Core Features & Use Cases

  • Generate a bun-runtime CLI from MCP definitions for portable, distributable tooling.
  • Inspect available MCP tools, perform remote authentication, and execute single calls or reusable CLI workflows.
  • Use Case: create a CLI wrapper around a specific MCP tool so teammates can invoke it without modifying Claude Code configurations.

Quick Start

Generate a bun-compiled CLI from your MCP source and output it to bin/<name>.

Frequently Asked Questions about mcp-to-cli

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

FAQPage Schema
How do I convert an MCP definition into a standalone CLI?

To convert an MCP definition into a standalone CLI, this Skill uses mcporter to parse MCP sources from Claude Code, Cursor, Codex, or HTTP, and generates a bun-runtime binary with a specified output path.

Can I run MCP tools without registering the server in Claude Code?

Yes, you can run MCP tools without registering the server in Claude Code by generating a standalone CLI wrapper or performing one-off tool invocations using mcporter.

How do I inspect available tools and authenticate remote MCP sources?

You can inspect available MCP tools, perform remote authentication, and execute single calls by parsing MCP sources from local or remote configurations using mcporter.

What artifacts are generated when building a portable CLI from an MCP?

Building a portable CLI from an MCP generates a bun-compiled binary in the bin/<name> directory and produces configuration artifacts in the config/mcporter.json file.

Does generating a CLI from MCP definitions require any specific runtime?

Generating a CLI from MCP definitions requires the bun runtime, as mcporter compiles the standalone tool wrappers into bun-runtime binaries for portable, distributable execution.