Practical overview
When it fits
Use Mcpc when MCP server discovery and interaction need to fit into terminal-based debugging, shell automation, or an agent workflow that has shell access.
Who it is for
- Developers who need to inspect or debug MCP servers from a terminal.
- People scripting repeatable MCP workflows in shell.
- AI-agent builders who want shell-accessible interaction with MCP servers.
Documented uses
- Connect to remote MCP servers over Streamable HTTP or local servers over stdio.
- List and call server tools, inspect tool details, read resources, retrieve prompts, and work with asynchronous tasks.
- Keep named sessions open across multiple servers and search tools across active sessions.
- Format results as JSON for scripts and shell pipelines.
Requirements & limits
The documented installation routes are Homebrew on macOS and Linux, or npm or Bun with Node.js or Bun installed. The repository specifies an Apache-2.0 license.
- Supports MCP connections over stdio and Streamable HTTP.
- Persistent sessions can be kept for multiple servers.
- JSON output is available for scripts and shell pipelines.
- Authenticated remote connections use documented OAuth 2.1 options; credentials use the OS keychain, with a file-based fallback described for headless Linux and CI.
- x402 payments are experimental and require a created or imported wallet funded with USDC on Base.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Connect to an MCP server and inspect its tools
Create a named session with a remote server, review its capabilities and list its available tools.
Before you start
- Install Mcpc using a documented method: Homebrew on macOS or Linux, or npm or Bun with Node.js or Bun installed.
- Have the address of a remote MCP server; OAuth login may be needed for an authenticated server.
Steps
For an OAuth-protected server, run
mcpc loginfollowed by the server address.Run
mcpc connectwith the server address and a session name, such as@test.Run
mcpc @testto view server information and capabilities.Run
mcpc @test tools-listto list available tools.
Expected outcome
A named session is connected, with the server’s capabilities and available tools accessible from the terminal.
Guide limitations
- The tools available for use depend on the connected server.
- The guide covers connection and inspection, not the behavior or results of any particular server tool.
Connect to a server in an MCP configuration file
Open a session to one MCP server referenced in a standard JSON configuration file and list its tools.
Before you start
- Install Mcpc using a documented method.
- Have an existing MCP JSON configuration file containing the server entry.
Steps
Run
mcpc connectwith the configuration-file path, a colon, the server entry name, and a session name; for example,mcpc connect .vscode/mcp.json:apify @my-apify.Run
mcpc @my-apify tools-list.
Expected outcome
Mcpc opens a named session to the configured server and displays its available tools.
Guide limitations
- The configuration file must contain the referenced entry.
- The guide lists tools but does not cover tool-specific arguments or results.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- apify/mcpc · Official homepage title · retained in its source language