mcpwrapped
A lightweight proxy that allows users to filter MCP tools by whitelisting specific ones, preventing context window clutter. It sits between an MCP client and server to control tool visibility while transparently forwarding other protocol messages.
README
mcpwrapped
A lightweight MCP (Model Context Protocol) proxy that sits between an MCP client and server. It allows you to filter available tools, preventing context window clutter by only exposing the tools you explicitly want to use.
Features
- Tool Filtering: Whitelist specific tools using the
--visible_toolsflag. - Transparent Proxy: Forwards all other MCP protocol messages (resources, prompts, etc.) unchanged.
- Easy Integration: Works with any MCP client that supports command-based server configuration.
Installation
npm install -g mcpwrapped
Usage
mcpwrapped wraps your existing MCP server command. You pass the filtering flags first, followed by the actual command to run the server.
Basic Syntax
mcpwrapped --visible_tools=tool1,tool2 <actual_command> [actual_args...]
Example: Using with MCP Inspector
If you are using the @modelcontextprotocol/inspector to test a server, you can configure it to use mcpwrapped.
- Create a config file (e.g.,
inspector-config.json):
{
"mcpServers": {
"my-wrapped-server": {
"command": "mcpwrapped",
"args": [
"--visible_tools=calculate_sum,get_weather",
"python",
"-m",
"my_mcp_server"
],
"env": {
"PYTHONPATH": "."
}
}
}
}
- Run the inspector:
npx @modelcontextprotocol/inspector --config ./inspector-config.json
Example: Claude Desktop Configuration
To use it with Claude Desktop, update your claude_desktop_config.json:
{
"mcpServers": {
"filesystem": {
"command": "mcpwrapped",
"args": [
"--visible_tools=read_file",
"npx",
"-y",
"@modelcontextprotocol/server-filesystem",
"/Users/username/Desktop"
]
}
}
}
In this example, only the read_file tool from the filesystem server would be visible to Claude, hiding write_file, list_directory, etc.
Configuration Flags
| Flag | Description | Example |
|---|---|---|
| <code>‑‑visible_tools</code> | Comma-separated list of tool names to expose. If omitted, all tools are hidden (or behavior depends on implementation, currently filters if flag is present). | <code>‑‑visible_tools=read_file,search</code> |
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
E2B
Using MCP to run code via e2b.