mcp-tool-search
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., "@mcp-tool-searchsearch for file-related tools"
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.
mcp-tool-search
A standalone MCP (Model Context Protocol) gateway/proxy server that lets any MCP-compatible client (Cursor, Claude Code, Codex, VSCode, Windsurf, Claude Desktop, Pi) search and call tools across multiple downstream MCP servers through a single mcp proxy tool.
Features
Single
mcpproxy tool (~200 tokens) for on-demand tool search/describe/callConnects to multiple downstream MCP servers (stdio, HTTP, SSE, StreamableHTTP)
Direct tool mode: expose individual MCP tools as native tools
Metadata caching with content-based invalidation
OAuth authentication support (authorization_code + client_credentials)
npx resolution (skip ~143MB npm parent process)
Output guarding (50KiB / 2000 line truncation)
Config compatible with standard MCP
mcpServersformatstdio transport only (all clients supported)
Builds with tsup (esbuild) — keeps
.tsimport extensions in source, compiles to single-file.jsbundle
Related MCP server: Multi MCP
Quick Start
Installation
npm install -g mcp-tool-searchOr build from source:
git clone https://github.com/ericnunes30/mcp-gateway-proxy.git
cd mcp-gateway-proxy
npm install
npm run buildConfiguration
Create a config file at ~/.config/mcp-tool-search/config.json:
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/dir"]
},
"github": {
"url": "https://api.github.com/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}CLI Usage
# Using --mcp-config (preferred)
node dist/cli.js --mcp-config ~/.config/mcp-tool-search/config.json
# --config also works as an alias
node dist/cli.js --config ~/.config/mcp-tool-search/config.jsonClient Configuration
Cursor
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"mcp-tool-search": {
"command": "mcp-tool-search",
"args": ["--mcp-config", "/path/to/config.json"]
}
}
}Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"mcp-tool-search": {
"command": "npx",
"args": ["mcp-tool-search", "--mcp-config", "/path/to/config.json"]
}
}
}Claude Code
Claude Code reads MCP server config from ~/.claude.json (home directory), not .claude/settings.json. On Windows, use the absolute path to node.exe.
{
"mcpServers": {
"mcp-tool-search": {
"type": "stdio",
"command": "C:/PROGRA~1/nodejs/node.exe",
"args": [
"G:/novosApps/mcp-tool-search/dist/cli.js",
"--mcp-config",
"C:/Users/Eric/.config/mcp-tool-search/config.json"
]
}
}
}Pi (with pi-mcp-extension)
Add to ~/.pi/agent/mcp.json:
{
"mcpServers": {
"mcp-tool-search": {
"command": "node",
"args": ["/path/to/mcp-gateway-proxy/dist/cli.js", "--mcp-config", "/path/to/config.json"],
"lifecycle": "eager"
}
}
}The proxy connects to all your downstream MCP servers. The Pi extension only needs to know about the proxy — no duplication of tools.
Pi agent → pi-mcp-extension → mcp-tool-search (proxy) → N downstream serversProxy Tool Usage
The mcp tool accepts these parameters:
Parameter | Type | Description |
| string | Tool name to call |
| string | Arguments as JSON string |
| string | Server name to connect |
| string | Tool name to describe |
| string | Search query |
| boolean | Treat search as regex |
| boolean | Include schemas in search |
| string | Filter to server |
| string | "ui-messages", "auth-start", "auth-complete" |
Examples
mcp({}) → Show server status
mcp({ server: "filesystem" }) → List tools from server
mcp({ search: "file" }) → Search tools
mcp({ describe: "read_file" }) → Show tool details
mcp({ connect: "github" }) → Connect to server
mcp({ tool: "read_file", args: '{"path":"/foo"}' }) → Call a tool
mcp({ action: "auth-start", server: "linear" }) → Start OAuth
mcp({ action: "auth-complete", server: "linear", args: '{"redirectUrl":"..."}' }) → Complete OAuthExample Output
mcp({}) →
MCP: 2/5 servers, 38 tools
✓ chrome-devtools (29 tools)
✓ pencil (9 tools)
○ stitch (not connected)
○ tavily (not connected)
○ computer-use (not connected)mcp({ search: "screenshot" }) →
Found 3 tools matching "screenshot":
chrome_devtools_take_screenshot
Take a screenshot of the page or element.
Parameters: format, quality, uid, fullPage, filePath
pencil_get_screenshot
Returns a screenshot of a node in a .pen file.
Parameters: filePath, nodeIdConfiguration Reference
Server Entry
Field | Type | Description |
| string | Command to run (stdio) |
| string[] | Arguments for command |
| Record<string,string> | Environment variables |
| string | HTTP/SSE/StreamableHTTP URL |
| Record<string,string> | HTTP headers |
| "stdio" | "http" | "sse" | "streamable-http" | Transport type |
| "http" | Alias for transport (standard MCP compatibility) |
| object | OAuth configuration |
| "lazy" | "eager" | "keep-alive" | Connection mode |
| number | Idle timeout (seconds) |
| boolean | string[] | Expose as direct tools |
| string[] | Tools to exclude |
| boolean | Expose resources as tools |
| "server" | "short" | "none" | Tool name prefix |
| number | Request timeout |
| boolean | Auto-start OAuth |
| string | Bearer token |
| string | Env var name for bearer token |
Settings (top-level)
Field | Type | Description |
| "server" | "short" | "none" | Global tool prefix |
| boolean | string[] | Global direct tools |
| boolean | Global auto-auth |
| number | Global idle timeout |
| number | Global request timeout |
| boolean | Disable proxy tool |
| string | Custom auth message |
Environment Variables
Variable | Description |
| Enable debug logging to stderr |
| Data directory override (default: |
| Direct tools filter (comma-separated, |
| npx cache TTL in ms (default: 24h) |
Architecture
┌──────────────────┐ stdio ┌──────────────────┐
│ MCP Client │◄──────────────►│ mcp-tool-search │
│ (Cursor, etc.) │ JSON-RPC │ (this server) │
└──────────────────┘ └────────┬─────────┘
│
┌──────────────────────────┼──────────────────────────┐
│ │ │
┌─────┴─────┐ ┌──────┴──────┐ ┌──────┴──────┐
│ stdio │ │ HTTP/SSE │ │ Streamable │
│ server │ │ server │ │ HTTP │
└───────────┘ └─────────────┘ └─────────────┘Development
npm install # Install dependencies
npm run build # Build with tsup → dist/cli.js
npm run typecheck # Type-check with tsc (no emit)
npm test # Run vitest test suite (84 tests)Build System
The project uses tsup (powered by esbuild) for compilation:
Source code uses
.tsimport extensions (e.g.,import { foo } from "./types.ts")tsconfig.json has
noEmit: truefor type-checking onlytsup bundles everything into a single
dist/cli.jsfile (~150KB)Dependencies (
@modelcontextprotocol/sdk,open,recheck,typebox,zod) are externalized
Project Structure
src/
├── cli.ts # CLI entry point
├── server.ts # MCP server setup + stdio transport
├── state.ts # Gateway state factory
├── config/
│ ├── types.ts # Config types (McpConfig, ServerEntry, etc.)
│ ├── config.ts # Config loader + merge logic
│ ├── imports.ts # Config imports/expand logic
│ └── paths.ts # Config path resolution
├── cache/
│ ├── metadata-cache.ts # Metadata cache (hash-based invalidation)
│ └── tool-metadata.ts # Tool metadata builder + search
├── auth/
│ ├── auth-store.ts # Token storage (secure file permissions)
│ ├── oauth-provider.ts # OAuth client provider
│ ├── oauth-flow.ts # OAuth flow (start, complete, authenticate)
│ └── callback-server.ts # OAuth callback HTTP server
├── mcp/
│ ├── server-manager.ts # MCP server connection manager
│ ├── transport.ts # Transport creation (stdio/HTTP/SSE/StreamableHTTP)
│ └── npx-resolver.ts # npx package resolution (skip npm parent)
├── lifecycle/
│ ├── lifecycle.ts # Lifecycle manager (lazy/eager/keep-alive)
│ └── lazy-connect.ts # Lazy connect with 60s failure backoff
├── guard/
│ └── output-guard.ts # Output truncation (50KiB / 2000 lines)
├── tools/
│ ├── proxy.ts # Proxy tool definition + dispatch
│ ├── proxy-actions.ts # Proxy action handlers (search/describe/call/etc.)
│ ├── direct-tools.ts # Direct tool resolution + executor
│ └── tool-registrar.ts # MCP content transformation
├── handlers/
│ ├── list-tools.ts # ListToolsRequest handler
│ └── call-tool.ts # CallToolRequest handler
└── utils/
├── abort.ts # AbortSignal utilities
├── logger.ts # stderr-only logger
├── env.ts # Environment variable interpolation
└── utils.ts # General utilities (parallelLimit, etc.)License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityCmaintenanceA proxy server that unifies multiple MCP servers, enabling seamless tool, prompt, and resource management via the MetaMCP App.Last updated59154Apache 2.0
- AlicenseBqualityDmaintenanceA flexible proxy server that aggregates multiple backend MCP servers into a single interface using STDIO or SSE transports. It supports dynamic server management via an HTTP API and utilizes namespacing to prevent tool conflicts across connected services.Last updated31MIT

mcp-server-metatoolofficial
Alicense-qualityCmaintenanceA proxy MCP server that aggregates tools from multiple MCP servers and forwards calls to the appropriate server, used with the Metatool App for GUI tool management.Last updated5Apache 2.0- Alicense-qualityCmaintenanceA gateway that aggregates multiple MCP servers into a single endpoint, namespacing their tools and forwarding calls, so an agent connects to one MCP to access the entire stack.Last updatedMIT
Related MCP Connectors
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
A paid remote MCP for hosted MCP server, built to return verdicts, receipts, usage logs, and audit-r
A paid remote MCP for CLI tool MCP, built to return verdicts, receipts, usage logs, and audit-ready
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ericnunes30/mcp-gateway-proxy'
If you have feedback or need assistance with the MCP directory API, please join our Discord server