mcp-client

Connect to MCP servers and call their tools with JSON arguments.

Updated Aug 11, 2022
One-click install
npx skills add https://github.com/plipowczan/brain --skill mcp-client-plipowczan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-client
Source: https://github.com/plipowczan/brain/tree/main/.claude/skills/mcp-client
Command: npx skills add https://github.com/plipowczan/brain --skill mcp-client-plipowczan

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Connects to MCP servers and exposes their tools as on-demand skills to prevent context window bloat.

Core Features & Use Cases

  • Progressive disclosure of tool schemas: load on-demand when needed.
  • Unified discovery: list available tools from any MCP server.
  • Tool invocation: call tools with structured JSON arguments and receive results.
  • Use Case: Connect to Zapier, list tools, then call a tool with specific inputs.

Quick Start

Use the mcp-client skill to connect to a Zapier MCP server, enumerate tools, and execute a tool with arguments.

Frequently Asked Questions about mcp-client

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

FAQPage Schema
How do I expose MCP server tools as on-demand skills to prevent context window bloat?

MCP servers expose their tools as on-demand skills through mcp-client, which implements progressive disclosure to load tool schemas only when needed. This prevents context window bloat by keeping unused tool definitions out of the active context until explicitly requested.

How do I call MCP server tools with JSON arguments across different transports?

You call MCP server tools with structured JSON arguments across stdio, SSE, streamable HTTP, and FastMCP transports. The mcp-client implements a unified session interface with flexible config resolution and cross-transport tool execution to handle the invocation and return results.

Can I list available tools from any MCP server before loading them into the context window?

You can list available tools from any MCP server using the unified discovery feature without loading their full schemas into the context window. This allows you to enumerate tools first and then selectively load specific tool schemas on demand when needed.

Does mcp-client work with FastMCP and Zapier MCP servers?

mcp-client works with FastMCP and Zapier MCP servers, supporting multiple transports including stdio, SSE, and streamable HTTP. You can connect to a Zapier MCP server, enumerate its available tools, and execute a selected tool with specific JSON arguments.

What is the best way to prevent context window bloat when integrating multiple MCP servers?

The best way to prevent context window bloat when integrating multiple MCP servers is to use on-demand tool loading. mcp-client connects to servers and exposes tools as on-demand skills, implementing progressive disclosure so tool schemas are loaded only when explicitly needed.