mcpwrapped
Click on "Deploy 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
Related MCP server: mcp-compressor
Installation
npm install -g mcpwrappedUsage
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: 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 |
‑‑visible_tools | Comma-separated list of tool names to expose | ‑‑visible_tools=read,write |
How It Works
┌─────────────┐ ┌──────────────┐ ┌─────────────┐
│ MCP Client │ ◀──────▶│ mcpwrapped │ ◀──────▶│ MCP Server │
│ (Claude) │ │ (Proxy) │ │ │
│ │ │ │ │ │
└─────────────┘ └──────────────┘ └─────────────┘
│
└── Filters tool_list to only include
tools specified in --visible_toolsmcpwrapped 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.
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Security & DLP proxy for MCP: tool-poisoning scans, PII redaction on tool args/results. Beta.
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA configurable proxy that filters GitHub MCP server tools via YAML whitelist, reducing context consumption from 100+ tools to only the ones you need while providing meta-tools to discover available functionality.MIT
- AlicenseNot gradedqualityAmaintenanceA proxy server that wraps existing MCP servers to significantly reduce token consumption by compressing tool descriptions into a two-step interface. It enables users to integrate extensive toolsets without exceeding context limits or incurring high API costs.118Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA generic MCP proxy that filters which tools are exposed from a remote MCP server, reducing context window token usage by only loading the tools you actually need.161MIT
- AlicenseNot gradedqualityCmaintenanceA proxy MCP server that lazy-loads tools from configured servers on demand, reducing token usage and enabling mid-session server switching.12MIT