ck:use-mcp

Orchestrate MCP tool execution via Gemini CLI with stdin piping.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/DatTran26/KienTruThiHanh --skill ck-use-mcp-dattran26
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:use-mcp
Source: https://github.com/DatTran26/KienTruThiHanh/tree/main/.agents/skills/use-mcp
Command: npx skills add https://github.com/DatTran26/KienTruThiHanh --skill ck-use-mcp-dattran26

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate MCP operations and tool execution through a Gemini-based workflow.

Core Features & Use Cases

  • Integrated MCP execution via Gemini CLI with stdin piping to preserve the context budget.
  • Automatic fallback to the mcp-manager subagent when Gemini is unavailable or encounters issues.
  • Clear guidance that no new scripts should be created for maintenance or remediation, relying on existing tooling and guidelines.

Quick Start

Describe the MCP task you want to run, then pipe it to Gemini CLI for context-aware execution.

Frequently Asked Questions about ck:use-mcp

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

FAQPage Schema
How do I execute MCP tasks using the Gemini CLI?

To execute MCP tasks using the Gemini CLI, describe your desired MCP operation and pipe it to the CLI via stdin with auto-approval. This preserves your context budget while returning structured JSON results for reliable downstream integration.

What happens to my MCP workflow when Gemini is unavailable?

When Gemini is unavailable or encounters issues during your MCP workflow, the system automatically falls back to the mcp-manager subagent. This ensures your tool execution and context preservation tasks continue running without interruption.

How do I preserve context budget when automating MCP tool execution?

You preserve context budget during MCP tool execution by piping tasks directly to the Gemini CLI via stdin. This approach processes context-aware operations efficiently and returns structured JSON results for reliable integration with downstream agents.

Do I need to create new scripts for MCP task remediation?

No, you do not need to create new scripts for MCP task remediation. The workflow relies entirely on existing tooling, mcp-manager guidelines, and GEMINI.md configuration to discover, evaluate compatibility, and execute MCP operations.

Can I use a subagent for MCP tool discovery and compatibility evaluation?

Yes, you can use a subagent for MCP tool discovery and compatibility evaluation. The mcp-manager subagent acts as the automatic fallback when Gemini is unavailable, ensuring tool execution and context preservation still function properly.

What configuration is required to orchestrate MCP operations with Gemini?

Orchestrating MCP operations with Gemini requires the Gemini CLI, mcp-manager tooling, and GEMINI.md configuration. You consume these configurations to pipe tasks via stdin with auto-approval and receive structured JSON results.