Merge pull request #7 from warpdev/feat/grep

Add find-tools for grep-like tool search

Author: warpdev

.releaserc.json

@@ -13,7 +13,7 @@
 			{
 				"assets": [
 					"package.json",
-					"package-lock.json",
+					"pnpm-lock.yaml",
 					"CHANGELOG.md"
 				],
 				"message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"

CLAUDE.md

@@ -0,0 +1,115 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+This is an MCP (Model Context Protocol) Hub server that acts as a proxy/aggregator for multiple MCP servers. It bypasses tool limitations in AI assistants (especially Cursor's 40-tool limit) and provides a unified interface to multiple MCP servers.
+
+## Development Commands
+
+### Build and Run
+```bash
+# Install dependencies
+pnpm install
+
+# Build TypeScript to JavaScript
+pnpm build
+
+# Run the server (after building)
+pnpm start
+
+# Build and run in one command
+pnpm dev
+```
+
+### Development Workflow
+```bash
+# For testing changes locally with npx
+npm link  # Creates a global link to the local package
+npx mcp-hub-mcp  # Test the linked version
+
+# To unlink after testing
+npm unlink -g mcp-hub-mcp
+```
+
+### Release Process
+- Uses semantic-release with Conventional Commits
+- Commits should follow: `type(scope): description`
+- Types: feat, fix, docs, style, refactor, perf, test, chore
+- Breaking changes: add `!` after type or `BREAKING CHANGE:` in body
+- Releases are automated via GitHub Actions on the main branch
+
+## Architecture
+
+### Core Components
+
+1. **src/index.ts** - Entry point that creates the MCP server with three tools:
+   - `list-all-tools`: Lists all available tools from connected servers
+   - `call-tool`: Executes a tool on a specific server
+   - `find-tools`: Grep-like search for tools matching regex patterns
+
+2. **src/server-manager.ts** - `McpServerManager` class that:
+   - Loads server configurations from JSON file
+   - Manages connections to multiple MCP servers
+   - Proxies tool calls to appropriate servers
+   - Handles server lifecycle and error recovery
+   - Implements `findTools` method for regex-based tool search
+
+3. **src/types.ts** - Type definitions and Zod schemas for:
+   - Server configuration validation
+   - MCP SDK type exports
+   - Configuration file structure
+   - Parameter schemas for all tools
+
+### Configuration
+
+The server configuration is loaded from (in order of precedence):
+1. Environment variable: `MCP_CONFIG_PATH`
+2. Command-line argument: `--config-path`
+3. Default location: `./mcp-config.json` or `{cwd}/mcp-config.json`
+
+Configuration format (Claude Desktop compatible):
+```json
+{
+  "mcpServers": {
+    "server-name": {
+      "command": "command-to-run",
+      "args": ["arg1", "arg2"],
+      "env": { "KEY": "value" }
+    }
+  }
+}
+```
+
+### Tool Naming Convention
+
+Tools from connected servers are prefixed with the server name:
+- Original tool: `list-files`
+- Through hub: `server-name__list-files`
+
+## Important Considerations
+
+1. **Error Handling**: The hub gracefully handles server connection failures and continues operating with available servers.
+
+2. **Environment Variables**: Server configurations can include environment variables that are passed to child processes.
+
+3. **Logging**: Uses console.error for error messages since stdout is reserved for MCP protocol communication.
+
+4. **No Tests**: Currently no test framework is set up. When implementing tests, consider:
+   - Unit tests for server-manager.ts logic
+   - Integration tests for MCP protocol handling
+   - Mock MCP server responses for testing
+
+5. **TypeScript Configuration**: 
+   - Target: ES2020
+   - Module: NodeNext with NodeNext resolution
+   - Strict mode enabled
+   - Outputs to `dist/` directory
+   - Declaration files generated
+
+6. **Dependencies**: 
+   - Keep dependencies minimal (currently only @modelcontextprotocol/sdk and zod)
+   - All types are exported from types.ts for consistency
+
+7. **Binary Execution**: Configured as npm binary `mcp-hub-mcp` with shebang in index.ts

README.md

@@ -8,9 +8,9 @@ A hub server that connects to and manages other MCP (Model Context Protocol) ser
 
 ## Overview
 
-This project builds an MCP hub server that can connect to other MCP servers, list their tools, and execute them.
-It is especially useful for bypassing Cursor’s 40-tool MCP limit.
-Even outside of Cursor, it helps reduce AI mistakes by hiding infrequently used tools.
+This project builds an MCP hub server that connects to and manages multiple MCP (Model Context Protocol) servers through a single interface.
+It helps prevent excessive context usage and pollution from infrequently used MCPs (e.g., Atlassian MCP, Playwright MCP) by allowing you to connect them only when needed.
+This reduces AI mistakes and improves performance by keeping the active tool set focused and manageable.
 
 ## Key Features
 
@@ -40,13 +40,6 @@ Add this to your `mcp.json`:
 }
 ```
 
-### System Prompt (or Cursor Rules)
-
-```
-Before processing a user's request, you must use the "list_all_tools" command to identify which tools are available.
-```
-
-This ensures that the AI assistant will always check available tools before attempting to use them.
 
 ## Installation and Running
 
@@ -185,6 +178,71 @@ Calls a tool on a specific server.
 }
 ```
 
+### 3. `find-tools`
+
+Find tools matching a regex pattern across all connected servers (grep-like functionality).
+
+- `pattern`: Regex pattern to search for in tool names and descriptions
+- `searchIn`: Where to search: "name", "description", or "both" (default: "both")
+- `caseSensitive`: Whether the search should be case-sensitive (default: false)
+
+```json
+{
+  "name": "find-tools",
+  "arguments": {
+    "pattern": "file",
+    "searchIn": "both",
+    "caseSensitive": false
+  }
+}
+```
+
+Example patterns:
+- `"file"` - Find all tools containing "file"
+- `"^read"` - Find all tools starting with "read"
+- `"(read|write).*file"` - Find tools for reading or writing files
+- `"config$"` - Find tools ending with "config"
+
+Example output:
+```json
+{
+  "filesystem": [
+    {
+      "name": "readFile",
+      "description": "Read the contents of a file",
+      "inputSchema": {
+        "type": "object",
+        "properties": {
+          "path": {
+            "type": "string",
+            "description": "Path to the file to read"
+          }
+        },
+        "required": ["path"]
+      }
+    },
+    {
+      "name": "writeFile",
+      "description": "Write content to a file",
+      "inputSchema": {
+        "type": "object",
+        "properties": {
+          "path": {
+            "type": "string",
+            "description": "Path to the file to write"
+          },
+          "content": {
+            "type": "string",
+            "description": "Content to write to the file"
+          }
+        },
+        "required": ["path", "content"]
+      }
+    }
+  ]
+}
+```
+
 ## Commit Message Convention
 
 This project follows [Conventional Commits](https://www.conventionalcommits.org/) for automatic versioning and CHANGELOG generation.

package.json

@@ -25,14 +25,14 @@
 	"author": "",
 	"license": "MIT",
 	"dependencies": {
-		"@modelcontextprotocol/sdk": "^1.9.0",
-		"zod": "^3.22.4"
+		"@modelcontextprotocol/sdk": "^1.13.0",
+		"zod": "^3.25.67"
 	},
 	"devDependencies": {
-		"@types/node": "^18.19.3",
 		"@semantic-release/changelog": "^6.0.3",
 		"@semantic-release/git": "^10.0.1",
-		"semantic-release": "^21.0.7",
-		"typescript": "^5.3.3"
+		"@types/node": "^22.15.32",
+		"semantic-release": "^24.2.5",
+		"typescript": "^5.8.3"
 	}
 }