Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcpwrappedlist the tools that are currently whitelisted"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcpwrapped
mcpwrapped is 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_toolsflagTransparent 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
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
Example: Claude Desktop Configuration
To use it with Claude Desktop, update your claude_desktop_config.json:
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 |
‑‑visible_tools | Comma-separated list of tool names to expose | ‑‑visible_tools=read,write |
How It Works
mcpwrapped acts as a transparent proxy that:
Spawns the actual MCP server with the provided command
Intercepts messages from the server
Filters the
toolslist in initialization messages to only include allowed toolsPasses through all other messages unchanged (resources, prompts, tool calls, etc.)
License
MIT License - see LICENSE for details.