docs: Update mcpc MCP CLI client with new capabilities in Example Clients#2576
Open
jancurn wants to merge 7 commits intomodelcontextprotocol:mainfrom
Open
docs: Update mcpc MCP CLI client with new capabilities in Example Clients#2576jancurn wants to merge 7 commits intomodelcontextprotocol:mainfrom
mcpc MCP CLI client with new capabilities in Example Clients#2576jancurn wants to merge 7 commits intomodelcontextprotocol:mainfrom
Conversation
Update the mcpc client listing to reflect its full capabilities including async tasks, DCR, OAuth 2.1 with PKCE, cross-session discovery, MCP proxy sandboxing, interactive shell, schema validation, and x402 payments. https://claude.ai/code/session_01Y6Ksa3V6XWtwLXDFVGn3Cz
Adjust mcpc description based on Jan Curn's MCP Dev Summit NYC talk. Lead with the core value proposition: agents only need Bash() to access MCP, progressive tool discovery avoids context bloat, and shell scripts are more token-efficient than naive tool calling. Reorder features to highlight code mode and discovery first, add "no LLM required" detail. https://claude.ai/code/session_01Y6Ksa3V6XWtwLXDFVGn3Cz
Reframe opening around the "MCP haters are only half right" thesis: CLI and MCP are complementary, not competing. Call out the naive MCP anti-pattern (dumping tools into context), highlight self-documenting --help discovery, and clarify the division of concerns (MCP for remote, shell for local). Add "production-ready" to the lightweight bullet. https://claude.ai/code/session_01Y6Ksa3V6XWtwLXDFVGn3Cz
Replace editorial/marketing language with factual description matching the style of other entries. Lead with what mcpc does (maps MCP to CLI commands, single Bash() call) rather than making arguments about the ecosystem. Soften bullet claims to be descriptive rather than comparative. https://claude.ai/code/session_01Y6Ksa3V6XWtwLXDFVGn3Cz
mcpc MCP CLI client with new capabilities in Example Clients
SamMorrowDrums
approved these changes
Apr 15, 2026
Contributor
SamMorrowDrums
left a comment
There was a problem hiding this comment.
@jancurn I'm surprised to see the specific call-out for DCR considering it's officially only a fallback for CIMD at this stage (don't know if it's supported in mcpc though).
Otherwise seems good to me.
Contributor
Author
|
@SamMorrowDrums thanks for the feedback, mcpc supports DCR, I'm also reviewing the support for CIMD right now. |
Contributor
Author
|
CIMD support added: apify/mcpc#164 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updated the mcpc MCP CLI client documentation in Example Clients to reflect its current capabilities and positioning as a comprehensive, spec-compatible CLI client for the Model Context Protocol.
Key Changes
https://claude.ai/code/session_01Y6Ksa3V6XWtwLXDFVGn3Cz