ck:use-mcp

Execute MCP tools via Gemini CLI with structured JSON output.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/hidonguyen/trade-ops --skill ck-use-mcp-hidonguyen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:use-mcp
Source: https://github.com/hidonguyen/trade-ops/tree/main/.opencode/skills/use-mcp
Command: npx skills add https://github.com/hidonguyen/trade-ops --skill ck-use-mcp-hidonguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Utilizes MCP execution via Gemini CLI to maintain context budgets while coordinating multiple MCP-enabled tools with a resilient fallback pathway.

Core Features & Use Cases

  • Orchestrates MCP tool discovery and execution through Gemini CLI to preserve context budget.
  • Provides fallback to mcp-manager subagent and ck:mcp-builder to repair tools without scripts.
  • Ensures non-create script rule and explicit guidance for tool integration in a multi-tool MCP workflow.

Quick Start

Pass your task as an argument to the Gemini CLI via stdin to start MCP tool 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 automate MCP tool execution while preserving my context budget?

When Gemini CLI is unavailable, MCP tool execution falls back to the mcp-manager subagent and ck:mcp-builder to repair and run tools without scripts. This ensures your multi-tool MCP workflow continues operating with clear fallback paths.

Do I need to pipe stdin to initialize MCP operations with Gemini CLI?

Yes, the Gemini CLI automatically loads the GEMINI.md file during MCP tool execution. This auto-loading mechanism ensures proper context and configuration are applied when passing your task as an argument via stdin.

How do I handle MCP tool failures without scripts in a multi-tool workflow?

MCP tool execution outputs structured JSON responses after processing through Gemini CLI or the fallback subagent. This structured format provides clear, parseable results for your context-preserving MCP operations across different tools.

What is the best way to run context-preserving MCP operations across different tools?

Yes, you can integrate multiple MCP-enabled tools in a single workflow using this orchestration approach. It enforces a non-create script rule and provides explicit guidance for tool integration, ensuring smooth multi-tool MCP operations.