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
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
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: 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):
Run the inspector:
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. If omitted, all tools are hidden (or behavior depends on implementation, currently filters if flag is present). | ‑‑visible_tools=read_file,search |