Mcpc MCP Server
Execute MCP protocol operations directly from your terminal using shell commands.
Data last scanned yesterday · Reviewed today
Overview
Mcpc functions as a universal command-line interface for the Model Context Protocol. By mapping MCP operations like tools, resources, and prompts to shell commands, it allows developers to debug servers manually or script complex automation flows using standard tools like jq and xargs.
Our verdict
With a security score of 48/100, this tool is classified as high risk primarily because its authentication and read-only mechanisms have not yet undergone an editorial review. While it offers advanced features like OAuth 2.1 and AI sandboxing, users should exercise caution until further verification is performed. It is suitable for developers debugging MCP workflows but should be used carefully in environments handling sensitive credentials.
- Supports persistent sessions for multiple parallel server connections.
- Small footprint with only 10 direct dependencies.
- Actively maintained with updates occurring as recently as four days ago.
- Includes experimental support for x402 agentic payments.
- Lacks external editorial review for security-critical authentication features.
- Community-maintained status means there is no official vendor oversight.
- Read-only mode implementation remains unverified by independent reviewers.
Setup
{
"mcpServers": {
"mcpc": {
"args": [
"-y",
"@apify/mcpc"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What operating systems are supported by mcpc?
The client works on macOS, Windows, and Linux.
›How does mcpc store credentials on Linux?
It uses the OS keychain via the Secret Service API by default. On headless or CI systems, it falls back to a file-based store at ~/.mcpc/credentials.json with restricted permissions.
›Does mcpc require an LLM to function?
No, the client is a lightweight tool that operates independently and does not use LLMs on its own.
›Can mcpc interact with local MCP servers?
Yes, you can connect to local MCP servers by referencing an MCP configuration file via the connect command.
›Does mcpc support secure authentication protocols?
Yes, it includes full OAuth 2.1 support with CIMD and DCR, using the OS keychain for secure credential storage.
Alternatives
Changelog
Badge
Maintain this server? Add the live badge to your README.