mcp-client

Access external MCP servers by listing tools and calling them via a unified session interface.

810|213|Updated Jan 24, 2026

Search Tags:#automation #integration #cli #mcp #progressive-disclosure #tool-discovery #external-servers

Ready to run

npx skills add https://github.com/coleam00/second-brain-skills --skill mcp-client-coleam00

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mcp-client
Source: https://github.com/coleam00/second-brain-skills/tree/main/.claude/skills/mcp-client
Command: npx skills add https://github.com/coleam00/second-brain-skills --skill mcp-client-coleam00

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp, fastmcp, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill enables deterministic, on-demand access to external MCP servers by wrapping them as skills to prevent context window bloat from tool definitions and to keep Claude Code lean during multi-server workflows.

Core Features & Use Cases

On-demand tool discovery: List and load tool schemas from any MCP server only when needed.
Unified session interface: Interact with stdio, SSE, streamable HTTP, and FastMCP transports through a single client.
Cross-server integration: Bridge Zapier, Sequential Thinking, GitHub, filesystem, and other MCP servers without leaking context into prompts.

Quick Start

Use the mcp-client to connect to an MCP server, list its tools, or call a tool. Example: list servers, then inspect and invoke a tool with a JSON payload.

Frequently Asked Questions about mcp-client

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

FAQPage Schema

How do I connect to external MCP servers without bloating my context window?▼

You can wrap external MCP servers as skills to enable deterministic, on-demand access to tool schemas, preventing context window bloat from tool definitions during multi-server workflows.

Can I use a single client to interact with stdio, SSE, and streamable HTTP MCP transports?▼

Yes, the mcp-client provides a unified session interface that supports stdio, SSE, streamable_http, and fastmcp transports through a single client for transport-agnostic loading.

How do I discover and call tools across different MCP servers like GitHub or Zapier?▼

Use the mcp-client to list servers, inspect tool schemas dynamically via frontmatter metadata, and invoke tools with a JSON payload across GitHub, Zapier, and filesystem MCP servers.

Does mcp-client support on-demand tool discovery for cross-server integration?▼

Yes, it supports on-demand tool discovery by listing and loading tool schemas from any MCP server only when needed, bridging cross-server workflows without leaking context into prompts.

Why does my context window fill up when running multi-server MCP workflows?▼

Context window bloat occurs when tool definitions from multiple MCP servers load simultaneously, but wrapping them as skills keeps the environment lean by loading schemas on-demand.

What is the best way to manage multiple MCP server connections in Claude Code?▼

The best way is using a unified session interface that wraps external servers as skills, applying dynamic tool discovery to keep Claude Code lean during multi-server workflows.