Invoke MCP server tools, resources, and prompts from a local CLI.
npx skills add https://github.com/smithery-ai/mcp-to-cli --skill mcp-cli-smithery-ai
Please help me install this Agent Skill. Skill: mcp-cli Source: https://github.com/smithery-ai/mcp-to-cli/tree/main Command: npx skills add https://github.com/smithery-ai/mcp-to-cli --skill mcp-cli-smithery-ai
Many agents and developer tools must reconnect to remote MCP servers individually, which leads to repeated authorization flows, fragmented credentials, and excessive context usage. This CLI centralizes named connections locally so you can connect once and invoke tools, resources, and prompts from any shell or scripted workflow without reauthenticating each time.
Use mcp-cli to connect to a server with no browser by running the connect command with the --no-open flag, save the connection under a name, and then run the named connection's tools list to see available tools.
High-intent search queries and answers about installing and using this skill.
You can invoke remote MCP tools from the command line by using a CLI that connects to remote MCP servers, allowing you to list, inspect, and call tools with JSON arguments while validating them locally against their schemas.
OAuth PKCE authentication for remote MCP connections uses a local callback server to capture tokens, with optional ngrok tunneling for public callbacks, ensuring secure authorization flows without repeated logins.
Yes, you can manage multiple MCP server connections using nested profiles that maintain inherited connections and per-profile auth state, which is ideal for separating staging, production, or multi-tenant workflows.
The MCP CLI uses Streamable HTTP with SSE fallback for transport, ensuring robust connectivity and providing sensible error messages when communicating with remote MCP servers.
Yes, you need Bun to operate the MCP command line interface, which manages profile-specific connection and authentication state stored locally under the ~/.mcp-to-cli directory.
MCP tool calls fail when arguments are invalid because the CLI validates them locally against the tool's JSON schema before execution, preventing malformed requests from reaching the remote server.
aayushsoamRun, install, bundle, and test JavaScript apps with Bun.
DemonDamonDiscover AgentCard capabilities and invoke remote A2A skills as tools.
plipowczanConnect to MCP servers and call their tools with JSON arguments.
mattwoodcoDeploy a remote MCP server with OAuth 2.1 and PKCE authentication.
