mcp-client

Connect Claude to MCP servers with on-demand tool schema loading.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill enables Claude to connect to external MCP servers and load tool schemas on demand, reducing context window consumption.

Core Features & Use Cases

  • On-demand tool discovery: List tools from any configured MCP server without loading all tool schemas upfront.
  • Unified tool execution: Call tools across different transports (stdio, sse, streamable_http, fastmcp) with a single interface.
  • Remote and local integrations: Connect to Zapier, Sequential Thinking, GitHub, filesystem, and more through a single MCP client.

Quick Start

Use the mcp-client to list configured servers, inspect available tools, and execute a tool against a configured MCP server.

Frequently Asked Questions about mcp-client

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

FAQPage Schema
How do I connect Claude to an external MCP server without consuming the context window?

You can connect Claude to an MCP server using progressive disclosure to load tool schemas on demand, reducing context window consumption. This client provides a unified session for listing tools and executing tool calls across remote and local servers.

What MCP server transports can I use to connect and execute tool calls?

The MCP client supports multiple transports: stdio, sse, streamable_http, and fastmcp. This allows you to connect to and execute tool calls across different remote and local server configurations through a single interface.

Can I use a single MCP client to integrate Zapier, GitHub, and local filesystems?

Yes, you can connect to Zapier, Sequential Thinking, GitHub, and filesystems through a single MCP client. It provides a unified session for discovering and executing tools across these remote and local integrations.

How do I list available tools from a configured MCP server?

You can list tools from any configured MCP server without loading all tool schemas upfront. The client uses on-demand tool discovery, allowing you to inspect available tools and execute specific calls as needed.

Why does loading all MCP tool schemas upfront cause issues and how is it fixed?

Loading all MCP tool schemas upfront consumes excessive context window space. This is fixed by using progressive disclosure to load tool schemas on demand, ensuring you only load the specific tools you need when you need them.